unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mark H Weaver <mhw@netris.org>
Cc: 36992@debbugs.gnu.org
Subject: bug#36992: linux-libre-5.2.7 failed to build on armhf and aarch64; why?
Date: Fri, 09 Aug 2019 23:17:07 +0200	[thread overview]
Message-ID: <87zhkiujho.fsf@elephly.net> (raw)
In-Reply-To: <87ftmafa6u.fsf@netris.org>


Hi Mark,

> linux-libre-5.2.7 failed to build on Berlin due to a dependency failure:
>
>   https://ci.guix.gnu.org/search?query=linux-libre-5
>   https://ci.guix.gnu.org/build/1556871/details
>   https://ci.guix.gnu.org/build/1556831/details
>
> I guess that the deblobbing derivation probably failed, but I don't see
> a way to confirm this, or to find out what specifically went wrong.
>
> Specifically, I'd like to know:
>
> (1) Which derivations failed, that caused these dependency failures?

Some time ago I added a feature to Cuirass that allowed us to see what
dependency was responsible.  This worked through a somewhat awkward
processing of derivation files.  I guess that this no longer works since
the representation of derivation inputs has changed.

I’ll try to verify this later and fix this if possible.

It would be great if we didn’t have to do this and Cuirass were able to
record enough information when the build failed…

> (2) Were the failed build logs saved, and if so, how can I see them?

This also used to work before.  I’ll also look into that.  Previously
there would be a link to the logs on the details page.

> (3) Did the failed derivations time out, or was it another kind of failure?

I guess the logs — once available — will help us answer this question.

--
Ricardo

  reply	other threads:[~2019-08-09 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 18:46 bug#36992: linux-libre-5.2.7 failed to build on armhf and aarch64; why? Mark H Weaver
2019-08-09 21:17 ` Ricardo Wurmus [this message]
2022-06-10  1:07   ` Maxim Cournoyer

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=87zhkiujho.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=36992@debbugs.gnu.org \
    --cc=mhw@netris.org \
    /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).