Gianfranco Costamagna 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
>
> /<>/test/test-lib.sh: line 904: ./test19: No such file or
> directory
> make[2]: *** read jobs pipe: Bad file
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
/<>/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
David Bremner writes:
> Gianfranco Costamagna 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
>>
>> /<>/test/test-lib.sh: line 904: ./test19: No such file or
>> directory
>>
Am Do., 6. Okt. 2022 um 18:34 Uhr schrieb David Bremner :
>
> Michael J Gruber 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
Michael J Gruber 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
Michael J Gruber writes:
> Could it be that within a parallel make session, that gcc-make-call
> gets delegated to the master make jobserver and thus gcc returns too
> early? Wild speculation, I admit.
That's the kind of thing I would consider a bug in gcc.
> I haven't checked the code, but
