GNU bug report logs - #36992
linux-libre-5.2.7 failed to build on armhf and aarch64; why?

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36992 in the body.
You can then email your comments to 36992 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: bug-guix <at> gnu.org
Subject: linux-libre-5.2.7 failed to build on armhf and aarch64; why?
Date: Fri, 09 Aug 2019 14:46:38 -0400

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?
(2) Were the failed build logs saved, and if so, how can I see them?
(3) Did the failed derivations time out, or was it another kind of failure?

Can someone help me find out what's going on here?

     Thanks,
       Mark

Message #8 received at 36992 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Mark H Weaver <mhw <at> netris.org>
Cc: 36992 <at> debbugs.gnu.org
Subject: Re: bug#36992: linux-libre-5.2.7 failed to build on armhf and aarch64; why?
Date: Fri, 09 Aug 2019 23:17:07 +0200

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

Message #13 received at 36992-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: Mark H Weaver <mhw <at> netris.org>, 36992-done <at> debbugs.gnu.org
Subject: Re: bug#36992: linux-libre-5.2.7 failed to build on armhf and
 aarch64; why?
Date: Thu, 09 Jun 2022 21:07:09 -0400

Hello,

Ricardo Wurmus <rekado <at> elephly.net> writes:

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

Cuirass has evolved a lot since; then. It's now possible to follow the
chain of failed dependency and the logs should be saved.

Closing.

Thanks,

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.