List for cgit developers and users
 help / color / mirror / Atom feed
From: list at eworm.de (Christian Hesse)
Subject: failing tests with git v2.22.0-rc3
Date: Tue, 11 Jun 2019 12:45:49 +0200	[thread overview]
Message-ID: <20190611124549.7a8d7ed5@leda> (raw)
In-Reply-To: <20190604145713.452d7744@leda>

Christian Hesse <list at eworm.de> on Tue, 2019/06/04 14:57:
> Hello everybody,
> 
> with git v2.22.0-rc3 we have failing tests:
> 
> [ log snipped ]
> 
> 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?

This is due to tr2_sysenv_load() being called in trace2_initialize_fl(),
which calls read_very_early_config() and thus loads the config before we can
unset the environment variables. No idea how to solve this as things happen
before our own code kicks in.
-- 
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/20190611/d374e94a/attachment.asc>


      reply	other threads:[~2019-06-11 10:45 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 ` failing tests with git v2.22.0-rc3 (was: [PATCH 1/1] RFC: git: update to v2.22.0-rc0) list
2019-06-11 10:45   ` list [this message]

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=20190611124549.7a8d7ed5@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).