unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Gianfranco Costamagna <locutusofborg@debian.org>,
	"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Test failure in Ubuntu 22.04 and 22.10 (new test)
Date: Thu, 06 Oct 2022 08:22:52 -0300	[thread overview]
Message-ID: <87ilkxxkkz.fsf@tethera.net> (raw)
In-Reply-To: <87leptxmg1.fsf@tethera.net>

David Bremner <david@tethera.net> writes:

> Gianfranco Costamagna <locutusofborg@debian.org> writes:
>
>> Hello, the test is now failing in Ubuntu 22.04 (last LTS), when run with parallel > 1
>>
>> (version 0.37)
>>
>> e.g. here you can see a build fail
>>
>> /<<PKGBUILDDIR>>/test/test-lib.sh: line 904: ./test19: No such file or directory
>> make[2]: *** read jobs pipe: Bad file descriptor.  Stop.
>> make[2]: *** Waiting for unfinished jobs....
>> lto-wrapper: fatal error: make returned 2 exit status
>>
>>
>> https://launchpadlibrarian.net/627359226/buildlog_ubuntu-kinetic-amd64.notmuch_0.37-1ubuntu3_BUILDING.txt.gz
>>
>> Running dh_auto_test with --no-parallel flag works as workaround, and using last gmame from Debian doesn't fix the issue
>> (you can see in the above build log the version that is used Get:2 http://ppa.launchpadcontent.net/costamagnagianfranco/locutusofborg-ppa/ubuntu kinetic/main amd64 libgmime-3.0-0 amd64 3.2.13+dfsg-2 [177 kB] )
>>
>>
>> Looks like all the tests using test_private_C function are failing, but I can't figure out where its the race-condition.
>
> It's especially puzzling as make -j$(whatever) should not enable running
> the test suite in parallel, only the presence of (GNU|moreutils)
> parallel. So it's like something is cleaning up after the test suite too
> early.

A second look at the log I see lto-wrapper failing, presumably in trying
to the test binaries.  I can duplicate the problem by adding -flto to
CFLAGS and CXXFLAGS. It _looks_ like lto-wrapper is invoking make
internally? 

Anyway, if you have an lto expert (or you are one), it would be
interesting to get feedback on what those error messages mean, and why
they are only triggered under make -j.


d\r

  reply	other threads:[~2022-10-06 11:22 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 [this message]
     [not found]       ` <CAA19uiS0EfEaUdgC0FJU1hzDH-_vXFL6Cn8Et7yZgcXKuF49Wg@mail.gmail.com>
2022-10-06 16:34         ` David Bremner
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=87ilkxxkkz.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=locutusofborg@debian.org \
    --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).