From: list at eworm.de (Christian Hesse)
Subject: failing tests with git v2.22.0-rc3 (was: [PATCH 1/1] RFC: git: update to v2.22.0-rc0)
Date: Tue, 4 Jun 2019 14:57:13 +0200 [thread overview]
Message-ID: <20190604145713.452d7744@leda> (raw)
In-Reply-To: <20190513194436.20233-1-list@eworm.de>
Hello everybody,
with git v2.22.0-rc3 we have failing tests:
not ok 1 - do not access $HOME:
#
# test_no_home_access ''
#
not ok 2 - do not access $HOME: foo
#
# test_no_home_access 'foo'
#
not ok 3 - do not access $HOME: foo/refs
#
# test_no_home_access 'foo/refs'
#
not ok 4 - do not access $HOME: foo/log
#
# test_no_home_access 'foo/log'
#
not ok 5 - do not access $HOME: foo/tree
#
# test_no_home_access 'foo/tree'
#
not ok 6 - do not access $HOME: foo/tree/file-1
#
# test_no_home_access 'foo/tree/file-1'
#
not ok 7 - do not access $HOME: foo/commit
#
# test_no_home_access 'foo/commit'
#
not ok 8 - do not access $HOME: foo/diff
#
# test_no_home_access 'foo/diff'
#
not ok 9 - do not access $HOME: foo/patch
#
# test_no_home_access 'foo/patch'
#
not ok 10 - do not access $HOME: foo/snapshot/master.tar.gz
#
# test_no_home_access 'foo/snapshot/master.tar.gz'
#
# failed 10 among 10 test(s)
This is caused by offending git upstream commit ("trace2: use system/global
config for default trace2 settings"):
https://github.com/git/git/commit/bce9db6de97c95882a7c46836bb6cc90acf0fef0
I did not yet have a deeper look. Is anybody familiar with this code and can
tell what goes wrong?
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20190604/631b3b4a/attachment.asc>
next prev parent reply other threads:[~2019-06-04 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 19:44 [PATCH 1/1] RFC: git: update to v2.22.0-rc0 list
2019-06-04 12:57 ` list [this message]
2019-06-11 10:45 ` failing tests with git v2.22.0-rc3 list
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190604145713.452d7744@leda \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).