From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 34461@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <87sgw2nxe5.fsf@gnu.org> (raw)
In-Reply-To: <20190212195400.GA30887@jasmine.lan> (Leo Famulari's message of "Tue, 12 Feb 2019 14:54:00 -0500")
Hi Leo,
Leo Famulari <leo@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’.
prev parent reply other threads:[~2019-03-04 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 19:54 bug#34461: Debugging build failures on Berlin / qemu-minimal-2.10 not available on Berlin build farm Leo Famulari
2019-02-12 19:59 ` bug#34461: Debugging build failures on Berlin Leo Famulari
2019-03-04 21:27 ` Ludovic Courtès [this message]
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=87sgw2nxe5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34461@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).