From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 36754@debbugs.gnu.org
Subject: bug#36754: New linux-libre failed to build on armhf on Berlin
Date: Mon, 22 Jul 2019 13:13:11 -0400 [thread overview]
Message-ID: <87zhl656xk.fsf@netris.org> (raw)
In-Reply-To: <87o91n3ps0.fsf@netris.org>
Hi Ricardo,
Interesting. I distinctly remember that there was no log file when I
looked last time. Hmm.
Anyway, it seems that now, all of the failed builds have either build
logs available or else information about which dependency failed. I
don't remember seeing any of this last time, but I'm glad to see it now.
A pattern has now emerged, but I don't know what it means. All of the
armhf kernel builds failed except for linux-libre-arm-veyron-5.2.2,
which succeeded:
https://ci.guix.gnu.org/build/1488502/details (arm-veyron-5.2.2)
Apart from this anomalous success, all of the armhf 5.2.2 and 4.19.60
have a truncated log file:
https://ci.guix.gnu.org/build/1488517/details (5.2.2)
https://ci.guix.gnu.org/build/1488503/details (4.19.60)
https://ci.guix.gnu.org/build/1488513/details (arm-generic-5.2.2)
https://ci.guix.gnu.org/build/1488519/details (arm-generic-4.19.60)
https://ci.guix.gnu.org/build/1488504/details (arm-omap2plus-5.2.2)
https://ci.guix.gnu.org/build/1488501/details (arm-omap2plus-4.19.60)
This pattern seems too regular to be a coincidence. Can we find out
which build machines were used for these builds?
All of the 4.14.134 builds failed in the deblobbing step, due to timeout
(1 hour of silence) while packing the linux-libre tarball:
https://ci.guix.gnu.org/build/1488514/details (4.14.134)
https://ci.guix.gnu.org/build/1488515/details (arm-generic-4.14.134)
https://ci.guix.gnu.org/build/1488512/details (arm-omap2plus-4.14.134)
I'm not sure how to deal with this. This is a computed origin, not a
normal package, and so I don't see a way to configure a longer timeout.
Perhaps I should make the tarball packing and unpacking operations
verbose, to work around the issue. Of course that's our usual practice,
but I find it suboptimal because any warnings will be buried in a
mountain of uninteresting output.
Thoughts? Anyway, thanks for looking into it.
Mark
next prev parent reply other threads:[~2019-07-22 17:15 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
2019-07-22 17:13 ` Mark H Weaver [this message]
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=87zhl656xk.fsf@netris.org \
--to=mhw@netris.org \
--cc=36754@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).