From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus 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 Message-ID: <87zhkiujho.fsf@elephly.net> References: <87ftmafa6u.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46749) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hwCGx-0007z8-Ir for bug-guix@gnu.org; Fri, 09 Aug 2019 17:18:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hwCGw-0000RT-Fm for bug-guix@gnu.org; Fri, 09 Aug 2019 17:18:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:34488) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hwCGw-0000RE-31 for bug-guix@gnu.org; Fri, 09 Aug 2019 17:18:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hwCGv-0004OX-T5 for bug-guix@gnu.org; Fri, 09 Aug 2019 17:18:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87ftmafa6u.fsf@netris.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Mark H Weaver Cc: 36992@debbugs.gnu.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=3Dlinux-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=E2=80=99ll try to verify this later and fix this if possible. It would be great if we didn=E2=80=99t have to do this and Cuirass were abl= e to record enough information when the build failed=E2=80=A6 > (2) Were the failed build logs saved, and if so, how can I see them? This also used to work before. I=E2=80=99ll also look into that. Previous= ly 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 failur= e? I guess the logs =E2=80=94 once available =E2=80=94 will help us answer thi= s question. -- Ricardo