From: Brice Waegeneire <brice@waegenei.re>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41661@debbugs.gnu.org
Subject: bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes
Date: Thu, 04 Jun 2020 13:02:29 +0000 [thread overview]
Message-ID: <eca4f8cc0d9d0efabf89318eac0f1fb8@waegenei.re> (raw)
In-Reply-To: <87mu5jauvq.fsf@gnu.org>
Hello,
On 2020-06-04 12:16, Ludovic Courtès wrote:
> Hi,
>
> Leo Famulari <leo@famulari.name> skribis:
>
>> We really need to improve our CI so that it's possible to discover
>> these
>> build failures. Currently it's quite hard to monitor if they get built
>> unless you just do `guix build foo`.
>
> Or ‘guix weather’, which is not worse than a web UI IMO.
+1 for CLI tools!
>> The last time this came up [0] it was said that maybe it's not really
>> correct to make these properties of the package, but rather of the CI
>> jobs. It makes sense but we need a solution, or stop supporting
>> underpowered architectures like armhf, because most of those machines
>> can't build this stuff themselves, and it's not good to advertise
>> support to people who will just be disappointed later.
>
> Yeah. I think we need to look at these on a case-by-case basis. Guile
> is one of those packages known to hit the max-silent-time of 1h (?)
> that’s configured on berlin. Hopefully it will no longer be the case
> starting from 3.0.3.
>
> What about Linux-libre? Does it hit the max absolute build time on
> armhf?
I misdiagnosed the issue, substitutes for it are available now and
previous
seems to be there too. IDK why it wasn't available before nor why I
couldn't manage to built it myself.
> As I wrote elsewhere, I think it makes more sense in a way to have
> those timeouts configured system-wide. But yeah, we need to be
> pragmatic.
>
> Thanks,
> Ludo’.
- Brice
next prev parent reply other threads:[~2020-06-04 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 13:15 bug#41661: [Cuirass] Doesn't honor 'timeout' nor 'max-silent-time' leading to mising substitutes Brice Waegeneire
2020-06-02 17:44 ` Leo Famulari
2020-06-04 12:16 ` Ludovic Courtès
2020-06-04 13:02 ` Brice Waegeneire [this message]
2021-03-25 13:02 ` Mathieu Othacehe
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=eca4f8cc0d9d0efabf89318eac0f1fb8@waegenei.re \
--to=brice@waegenei.re \
--cc=41661@debbugs.gnu.org \
--cc=ludo@gnu.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).