GNU bug report logs - #34461
Debugging build failures on Berlin / qemu-minimal-2.10 not available on Berlin build farm

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 34461 in the body.
You can then email your comments to 34461 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: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: Debugging build failures on Berlin / qemu-minimal-2.10 not available
 on Berlin build farm
Date: Tue, 12 Feb 2019 14:54:00 -0500

Substitutes of the hidden package qemu-minimal-2.10 are available from
<https://mirror.hydra.gnu.org> but not <https://berlin.guixsd.org>.

I'd like to fix this but I'm not sure how to start debugging things on
the Berlin build farm.

I know how to use the Hydra web interface to debug build failures but I
need help getting started with Berlin.

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

From: Leo Famulari <leo <at> famulari.name>
To: 34461 <at> debbugs.gnu.org
Subject: Re: Debugging build failures on Berlin
Date: Tue, 12 Feb 2019 14:59:32 -0500

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

I know this bug report is vague. Any guidance on a build debug workflow
for the Berlin build farm will be helpful.

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

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: 34461 <at> debbugs.gnu.org
Subject: Re: bug#34461: Debugging build failures on Berlin / qemu-minimal-2.10
 not available on Berlin build farm
Date: Mon, 04 Mar 2019 22:27:14 +0100

Hi Leo,

Leo Famulari <leo <at> famulari.name> skribis:

> Substitutes of the hidden package qemu-minimal-2.10 are available from
> <https://mirror.hydra.gnu.org> but not <https://berlin.guixsd.org>.
>
> I'd like to fix this but I'm not sure how to start debugging things on
> the Berlin build farm.

I would get the .drv file name of that thing and then do:

  guix build --log-file /gnu/store/…-qemu-minimal.drv \
     --substitute-urls=https://berlin.guixsd.org

This should give you the URL of the failed build.

Alternately, you can also go directly to:

  https://berlin.guixsd.org/log/XYZ-qemu-minimal

where “XYZ-qemu-minimal” is the *output* file name of that thing (not
the .drv file name.)

If that is 404, then most likely the thing was never built.  To
determine why, one would have to inspect /var/log/cuirass.log from
berlin…

HTH!

Ludo’.

Previous Next

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