bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

["Ludovic Courtès" <ludo@gnu.org>]

Hi!

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Wed, May 03, 2023 at 09:29:49PM +0200, Ludovic Courtès wrote:
>> Hey Efraim,
>> 
>> Efraim Flashner <efraim@flashner.co.il> skribis:
>> 
>> > I reran it and got a different test failure
>> 
>> > FAIL: tests/starting-status.sh
>> 
>> Could you retry from the ‘master’ branch?  I pushed a couple of commits
>> since your message that probably fixed this one.
>> 
>> Thanks a lot for testing!
>
> I ran the build on aarch64 and on riscv64 from commit
> d6e4f59705f8526bea320a19e00d0aca552c1270. aarch64 for armhf succeeded (2
> cores on a pine64). aarch64 failed (6 cores on a pinebook pro) and
> riscv64 failed (2 cores on a starfive1). Second time through aarch64
> succeeded on the same machine (which was definitely not doing anything
> else at the time) and the riscv64 build succeeded on a 4 core starfive2.

I believe 7c79df11c7a9d938ed9b48e00c4366da95301d4b fixes a race
condition that these tests were showing: ‘herd stop root’ can return
before the shepherd process has terminated.

Could you try again?

For AArch64, what machine are you using, with what CPU?  There’s a
Guile (?) bug manifesting on the OverDrive 1000 that causes more or
less random test failures, unless you set GUILE_JIT_THRESHOLD=-1:

  https://github.com/wingo/fibers/issues/83

Thanks for your help!

Ludo’.