GNU bug report logs - #63178
shepherd 0.10.0-rc1 riscv64 build failure

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 63178 in the body.
You can then email your comments to 63178 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: bug-guix <at> gnu.org
Cc: ludo <at> gnu.org
Subject: shepherd 0.10.0-rc1 riscv64 build failure
Date: Sat, 29 Apr 2023 23:09:34 +0300

[Message part 1 (text/plain, inline)]

I replaced gettext with gettext-minimal and built from commit
ca3e31d6dbc0c4b811497edeb519a7060c2309f4. tests/stopping-status.sh
failed, build log attached.



-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[shepherd-riscv64-buildlog.gz (application/x-gunzip, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #8 received at 63178 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: 63178 <at> debbugs.gnu.org, ludo <at> gnu.org
Subject: Re: bug#63178: shepherd 0.10.0-rc1 riscv64 build failure
Date: Sat, 29 Apr 2023 23:26:59 +0300

[Message part 1 (text/plain, inline)]

I reran it and got a different test failure

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[shepherd-riscv64-buildlog2.gz (application/x-gunzip, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 63178 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 63178 <at> debbugs.gnu.org
Subject: Re: bug#63178: shepherd 0.10.0-rc1 riscv64 build failure
Date: Wed, 03 May 2023 21:29:49 +0200

Hey Efraim,

Efraim Flashner <efraim <at> 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!

Ludo’.

Message #14 received at 63178 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 63178 <at> debbugs.gnu.org
Subject: Re: bug#63178: shepherd 0.10.0-rc1 riscv64 build failure
Date: Thu, 4 May 2023 12:55:02 +0300

[Message part 1 (text/plain, inline)]

On Wed, May 03, 2023 at 09:29:49PM +0200, Ludovic Courtès wrote:
> Hey Efraim,
> 
> Efraim Flashner <efraim <at> 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 can run it through a few more times if you want.

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[shepherd-aarch64.log.gz (application/x-gunzip, attachment)]

[shepherd-riscv64.log.gz (application/x-gunzip, attachment)]

[signature.asc (application/pgp-signature, inline)]

Message #17 received at 63178 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 63178 <at> debbugs.gnu.org
Subject: Re: bug#63178: shepherd 0.10.0-rc1 riscv64 build failure
Date: Sat, 06 May 2023 19:59:39 +0200

Hi!

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

> On Wed, May 03, 2023 at 09:29:49PM +0200, Ludovic Courtès wrote:
>> Hey Efraim,
>> 
>> Efraim Flashner <efraim <at> 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’.

Message #20 received at 63178 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 63178 <at> debbugs.gnu.org
Subject: Re: bug#63178: shepherd 0.10.0-rc1 riscv64 build failure
Date: Sat, 6 May 2023 23:05:46 +0300

[Message part 1 (text/plain, inline)]

On Sat, May 06, 2023 at 07:59:39PM +0200, Ludovic Courtès wrote:
> Hi!
> 
> Efraim Flashner <efraim <at> flashner.co.il> skribis:
> 
> > On Wed, May 03, 2023 at 09:29:49PM +0200, Ludovic Courtès wrote:
> >> Hey Efraim,
> >> 
> >> Efraim Flashner <efraim <at> 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!

The pine64¹ is an allwinner A64 with 4 A53 cores and the pinebook pro²
uses an RK3399, 4 cores of A53 and 2 cores of A72. I've also picked up 2
rock64³s using an RK3328 with 4 A53 cores.

¹ https://wiki.pine64.org/wiki/PINE_A64
² https://wiki.pine64.org/wiki/Pinebook_Pro
³ https://wiki.pine64.org/wiki/ROCK64

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[signature.asc (application/pgp-signature, inline)]

Message #23 received at 63178 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: 63178 <at> debbugs.gnu.org
Subject: Re: bug#63178: shepherd 0.10.0-rc1 riscv64 build failure
Date: Sun, 07 May 2023 22:42:21 +0200

Hi!

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

> On Sat, May 06, 2023 at 07:59:39PM +0200, Ludovic Courtès wrote:

[...]

>> 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!
>
> The pine64¹ is an allwinner A64 with 4 A53 cores and the pinebook pro²
> uses an RK3399, 4 cores of A53 and 2 cores of A72. I've also picked up 2
> rock64³s using an RK3328 with 4 A53 cores.

OK, thanks.  Could you also check whether the Guile+Fibers snippet at
<https://github.com/wingo/fibers/issues/83> works on these machines?

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.