From: Mathieu Othacehe <othacehe@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 37246-done@debbugs.gnu.org
Subject: bug#37246: Cuirass builds spuriously fail with truncated build logs
Date: Thu, 25 Mar 2021 13:55:32 +0100 [thread overview]
Message-ID: <878s6b5r5n.fsf@gnu.org> (raw)
In-Reply-To: <875zmd9qn9.fsf@netris.org> (Mark H. Weaver's message of "Sat, 31 Aug 2019 13:43:27 -0400")
Hello,
> Previously, we've noticed that this problem happens quite frequently
> with armhf builds offloaded to hydra-slave{1,2,3}, which are hosted far
> from Berlin. The examples above show that this problem also happens
> with build slaves that are local to Berlin.
The Cuirass log mechanism has been rewritten and this bug should now be
fixed. Closing this one.
Thanks,
Mathieu
prev parent reply other threads:[~2021-03-25 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 17:43 bug#37246: Cuirass builds spuriously fail with truncated build logs Mark H Weaver
2021-03-25 12:55 ` Mathieu Othacehe [this message]
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=878s6b5r5n.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=37246-done@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).