bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

[Efraim Flashner]

[-- Attachment #1.1: Type: text/plain, Size: 377 bytes --]

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



-- 
Efraim Flashner   <efraim@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

[-- Attachment #1.2: shepherd-riscv64-buildlog.gz --]
[-- Type: application/x-gunzip, Size: 8601 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

[Efraim Flashner]

[-- Attachment #1.1: Type: text/plain, Size: 258 bytes --]

I reran it and got a different test failure

-- 
Efraim Flashner   <efraim@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

[-- Attachment #1.2: shepherd-riscv64-buildlog2.gz --]
[-- Type: application/x-gunzip, Size: 8545 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

[Ludovic Courtès]

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!

Ludo’.

bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

[Efraim Flashner]

[-- Attachment #1.1: Type: text/plain, Size: 1081 bytes --]

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 can run it through a few more times if you want.

-- 
Efraim Flashner   <efraim@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

[-- Attachment #1.2: shepherd-aarch64.log.gz --]
[-- Type: application/x-gunzip, Size: 8833 bytes --]

[-- Attachment #1.3: shepherd-riscv64.log.gz --]
[-- Type: application/x-gunzip, Size: 10864 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

[Ludovic Courtès]

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’.

bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 2071 bytes --]

On Sat, May 06, 2023 at 07:59:39PM +0200, Ludovic Courtès wrote:
> 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!

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@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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#63178: shepherd 0.10.0-rc1 riscv64 build failure

[Ludovic Courtès]

Hi!

Efraim Flashner <efraim@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’.