From: Ricardo Wurmus <rekado@elephly.net>
To: mhw@netris.org
Cc: 36754@debbugs.gnu.org
Subject: bug#36754: New linux-libre failed to build on armhf on Berlin
Date: Mon, 22 Jul 2019 18:10:46 +0200 [thread overview]
Message-ID: <87pnm2cant.fsf@elephly.net> (raw)
In-Reply-To: <87o91n3ps0.fsf@netris.org>
Mark H Weaver <mhw@netris.org> writes:
> Unfortunately, I'm unable to get *any* information about what went wrong
> from Cuirass. None of the failed builds have associated log files, and
> the build details page has no useful information either. For example:
>
> https://ci.guix.gnu.org/build/1488517/details
On that page I see a link to the build log, but it appears to be
truncated:
https://ci.guix.gnu.org/log/33hv7mij9bqqgf5hqwrw14106z9zgav9-linux-libre-5.2.2
Maybe the build node died before the build could be completed?
--
Ricardo
next prev parent reply other threads:[~2019-07-22 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 23:56 bug#36754: New linux-libre failed to build on armhf on Berlin Mark H Weaver
2019-07-22 16:10 ` Ricardo Wurmus [this message]
2019-07-22 17:13 ` Mark H Weaver
2019-07-23 16:46 ` Marius Bakke
2019-07-23 17:33 ` bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds (was: New linux-libre failed to build on armhf on Berlin) Mark H Weaver
2019-07-23 17:49 ` Mark H Weaver
2019-07-23 21:26 ` bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds Ludovic Courtès
2019-07-23 21:55 ` Ricardo Wurmus
2019-08-01 15:39 ` Ricardo Wurmus
2019-07-24 11:09 ` Mark H Weaver
2019-07-24 14:56 ` Ludovic Courtès
2019-08-01 14:09 ` Marius Bakke
2019-08-01 16:37 ` Mark H Weaver
2019-08-01 21:06 ` Ricardo Wurmus
2019-08-07 14:30 ` Ricardo Wurmus
2019-08-16 10:25 ` Ludovic Courtès
2019-09-12 8:41 ` Ludovic Courtès
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=87pnm2cant.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36754@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).