From: "Ludovic Courtès" <ludo@gnu.org>
To: Ivan Petkov <ivanppetkov@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Debugging CI build failures
Date: Wed, 15 May 2019 23:22:15 +0200 [thread overview]
Message-ID: <871s0zqupk.fsf@gnu.org> (raw)
In-Reply-To: <3FF875EF-7A1B-4BB5-ABB1-BDED21355F6F@gmail.com> (Ivan Petkov's message of "Sat, 11 May 2019 09:17:54 -0700")
Hi Ivan,
Ivan Petkov <ivanppetkov@gmail.com> skribis:
> I recently submitted some patches which updated the rust bootstrap process, but I noticed
> cuirass failed on building rust-1.24.1.x86_64-linux [1] (the build succeeded on my machine).
>
> I can’t seem to pull logs from cuirass either which makes me wonder if the issue was a build
> failure or something else. Am I missing something in the interface, or is there no way to
> see extra context like in Hydra?
The build farm’s log file is at <https://ci.guix.gnu.org/log/XYZ>, where
XYZ is the basename of one of the outputs of the derivation of
interest. For example:
https://ci.guix.gnu.org/log/cghjx256ls2hrpcjbv65vnmvqszddh4i-rust-1.24.1
Unless you have built it locally, the following command gives you the
URL:
guix build rust@1.24 --no-grafts --log-file
Now, the Cuirass Web and HTTP interfaces certainly leave a lot to be
desired, but you can help! :-) See Ricardo’s recent call for help on
guix-devel.
> (Speaking of Hydra, it seems like it is also stuck and not building anything or pulling in new
> commits, anyone know what is going on there?)
We’re now primarily focusing on ci.guix.gnu.org (aka. “berlin”), which
has more CPU power, so hydra.gnu.org may lag behind.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-05-15 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 16:17 Debugging CI build failures Ivan Petkov
2019-05-15 21:22 ` Ludovic Courtès [this message]
2019-05-16 5:11 ` Ivan Petkov
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=871s0zqupk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=ivanppetkov@gmail.com \
/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.
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).