Subject: Re: bug#76479: Shepherd 1.0.2 build failure on aarch64-linux
From: Ludovic Courtès <[email-masked]>
To: Zacchaeus <[email-masked]>
Cc: [email-masked]
Date: Sat, 15 Mar 2025 12:06:38 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Hi,

Zacchaeus <[email-masked]> skribis:

> I am having some trouble updating my home environment on aarch64-linux
> as shepherd fails to build.  I tried rebuilding multiple times hoping it
> would sort itself out like in #30299, but it might take a few more days
> if my puny Librem 5 needs to rebuild it 19 times :3.

The build log reads this:

--8<---------------cut here---------------start------------->8---
+ herd -s t-socket-2178 load root t-conf-2178
Loading t-conf-2178.
+ grep 'Respawning test3' t-log-2178
+ sleep 0.2
+ grep 'Respawning test3' t-log-2178
+ sleep 0.2
+ grep 'Respawning test3' t-log-2178
2025-02-17 17:31:42 Respawning test3.
+ herd -s t-socket-2178 status test3
+ grep running
+ cat t-log-2178
2025-02-17 17:31:18 GNU Shepherd 1.0.2 (Guile 3.0.9, aarch64-unknown-linux-gnu)
2025-02-17 17:31:18 bit-count is deprecated.  Use bitvector-count, or a loop over array-ref if array support is needed.
2025-02-17 17:31:18 scm_bitvector_length is deprecated.  Use scm_c_bitvector_length instead.
[…]
FAIL tests/respawn.sh (exit status: 1)
--8<---------------cut here---------------end--------------->8---

I believe this particular issue is a race condition in the test, fixed
with e658ec2d2616a48c21da4667cdf262cc1015c4e5.

Thanks,
Ludo’.