[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debugging CI build failures
From: |
Ludovic Courtès |
Subject: |
Re: Debugging CI build failures |
Date: |
Wed, 15 May 2019 23:22:15 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) |
Hi Ivan,
Ivan Petkov <address@hidden> 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 address@hidden --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’.