GNU bug report logs - #76479
Shepherd 1.0.2 build failure on aarch64-linux

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#76479: closed (Shepherd 1.0.2 build failure on aarch64-linux)
Date: Sat, 15 Mar 2025 11:07:02 +0000

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

Your message dated Sat, 15 Mar 2025 12:06:38 +0100
with message-id <87jz8qr1s1.fsf <at> gnu.org>
and subject line Re: bug#76479: Shepherd 1.0.2 build failure on aarch64-linux
has caused the debbugs.gnu.org bug report #76479,
regarding Shepherd 1.0.2 build failure on aarch64-linux
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
76479: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=76479
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Zacchaeus <eikcaz <at> zacchae.us>
To: bug-guix <at> gnu.org
Cc: ludo <at> gnu.org
Subject: Shepherd fails to build
Date: Mon, 17 Feb 2025 19:04:57 -0500

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

Hi all,

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.

Log attached.

eikcaz-

[bk8mziijpik5zl3chy57cs3cr7psfx-shepherd-1.0.2.drv.bz2 (application/octet-stream, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: Zacchaeus <eikcaz <at> zacchae.us>
Cc: 76479-done <at> debbugs.gnu.org
Subject: Re: bug#76479: Shepherd 1.0.2 build failure on aarch64-linux
Date: Sat, 15 Mar 2025 12:06:38 +0100

Hi,

Zacchaeus <eikcaz <at> zacchae.us> 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’.

Previous Next

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