unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 63178@debbugs.gnu.org
Subject: bug#63178: shepherd 0.10.0-rc1 riscv64 build failure
Date: Sat, 6 May 2023 23:05:46 +0300	[thread overview]
Message-ID: <ZFazGlzOVKTwiLwf@3900XT> (raw)
In-Reply-To: <87ild5ibn8.fsf@gnu.org>

[-- 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 --]

  reply	other threads:[~2023-05-06 20:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 20:09 bug#63178: shepherd 0.10.0-rc1 riscv64 build failure Efraim Flashner
2023-04-29 20:26 ` Efraim Flashner
2023-05-03 19:29   ` Ludovic Courtès
2023-05-04  9:55     ` Efraim Flashner
2023-05-06 17:59       ` Ludovic Courtès
2023-05-06 20:05         ` Efraim Flashner [this message]
2023-05-07 20:42           ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZFazGlzOVKTwiLwf@3900XT \
    --to=efraim@flashner.co.il \
    --cc=63178@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).