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 _______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-leave@notmuchmail.org