From: David Bremner <david@tethera.net>
To: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Test failure in Ubuntu 22.04 and 22.10 (new test)
Date: Thu, 06 Oct 2022 13:34:46 -0300 [thread overview]
Message-ID: <871qrkx655.fsf@tethera.net> (raw)
In-Reply-To: <CAA19uiS0EfEaUdgC0FJU1hzDH-_vXFL6Cn8Et7yZgcXKuF49Wg@mail.gmail.com>
Michael J Gruber <michaeljgruber+grubix+git@gmail.com> writes:
>
> Yes, lto-wrapper calls make.
>
> Are we compiling test functions on the fly during the test? In that
> case we need to make sure that each test depends on the build
> products, or else the test helper compilation and its users might run
> in parallel ...
Yes, we compile C code on the fly during the run of the tests. I'm not
really clear on what race condition you are anticipating, as neither the
compilation nor the other parts of the test are directly run by make.
Execution is sequential within each T*.sh file. Unless gcc is returning
before it has finished compilation (which I think we'd all agree would
be gcc bug), I don't see how a race can arise there. One thing I can
imagine happening is gcc's recursive invocation of make somehow fails
under make -j, possibly something to do with violated assumptions about
the jobserver and/or environment variables.
d
next prev parent reply other threads:[~2022-10-06 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1574005238.8760268.1665051216411.ref@mail.yahoo.com>
2022-10-06 10:13 ` Test failure in Ubuntu 22.04 and 22.10 (new test) Gianfranco Costamagna
2022-10-06 10:42 ` David Bremner
2022-10-06 11:22 ` David Bremner
[not found] ` <CAA19uiS0EfEaUdgC0FJU1hzDH-_vXFL6Cn8Et7yZgcXKuF49Wg@mail.gmail.com>
2022-10-06 16:34 ` David Bremner [this message]
2022-10-06 16:54 ` Michael J Gruber
2022-10-06 17:15 ` David Bremner
2022-10-10 17:27 ` Tomi Ollila
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qrkx655.fsf@tethera.net \
--to=david@tethera.net \
--cc=michaeljgruber+grubix+git@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).