From: Vincent Lefevre <vincent@vinc17.net>
To: libc-alpha@sourceware.org
Subject: Re: "make check" on git master fails with 175 FAIL and leaves processes behind on Debian/unstable
Date: Thu, 23 Feb 2023 15:00:59 +0100 [thread overview]
Message-ID: <20230223140059.GD2102@cventin.lip.ens-lyon.fr> (raw)
In-Reply-To: <2cb5e798-e411-6a95-eded-e08f08d9e957@linaro.org>
On 2023-02-22 17:00:35 -0300, Adhemerval Zanella Netto wrote:
> On 22/02/23 14:04, Vincent Lefevre wrote:
[...]
> > It seems that some tests may be confused by the
> > "LD_PRELOAD=libgtk3-nocsd.so.0" that comes from the gtk3-nocsd
> > Debian package (the INSTALL file is silent on this point).
> > But if I unset LD_PRELOAD and rerun "make check", I still get
> > these 8 failures, and the *.out and *.test-result files are not
> > updated. For instance:
>
> It seems that LD_PRELOAD is still set for some tests and it might indeed
> interfere on some results.
Well, this is because the corresponding *.out files have not been
rebuilt, i.e. the tests have been skipped, but the results of the
old tests with LD_PRELOAD set are still there and taken into account
in the summary at the end.
I've done a "make check" again with LD_PRELOAD unset, and I now
get 5 failures only, though nothing has changed on my side.
So, basically the issue is that tests are randomly skipped. I've
reported this bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=30157
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2023-02-23 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 14:56 Vincent Lefevre
2023-02-22 15:10 ` Carlos O'Donell
2023-02-22 15:38 ` Vincent Lefevre
2023-02-22 16:58 ` Florian Weimer
2023-02-22 17:04 ` Vincent Lefevre
2023-02-22 20:00 ` Adhemerval Zanella Netto
2023-02-23 14:00 ` Vincent Lefevre [this message]
2023-02-22 15:24 ` Andreas Schwab
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=20230223140059.GD2102@cventin.lip.ens-lyon.fr \
--to=vincent@vinc17.net \
--cc=libc-alpha@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).