Debugging CI build failures

Debugging CI build failures

[Ivan Petkov]

Hi Guix,

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?

(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?)

Thanks,
—Ivan

[1]: http://ci.guix.info/eval/5243?border-high-time=0&border-high-id=1303701 <http://ci.guix.info/eval/5243?border-high-time=0&border-high-id=1303701>

Re: Debugging CI build failures

[Ludovic Courtès]

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’.

Re: Debugging CI build failures

[Ivan Petkov]

Hi Ludo,

> On May 15, 2019, at 2:22 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> 
> 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 <https://ci.guix.gnu.org/log/cghjx256ls2hrpcjbv65vnmvqszddh4i-rust-1.24.1>

I think I had tried this earlier but I got a 404 error. Maybe the package was
retried sometime later. I’ll keep this in mind for next time!

> 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.

I’ll check it out!

—Ivan