From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org
Cc: Leo Famulari <leo@famulari.name>
Subject: Re: Missing substitutes and TIMEOUT property (Racket, MAME)
Date: Tue, 03 Mar 2020 14:48:18 +0100 [thread overview]
Message-ID: <87tv354kil.fsf@nckx> (raw)
In-Reply-To: <87wo8122qu.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Pierre,
Pierre Neidhardt 写道:
> Leo Famulari <leo@famulari.name> writes:
>
>> The logs of the failing builds should say if the failure was
>> caused by
>> timeout or exceeding the maximum "silent time" (time without
>> any output
>> from the build).
>
> If I look at failed builds for Racket or MAME, I get this:
>
> http://ci.guix.gnu.org/build/2290964/details
> http://ci.guix.gnu.org/build/2293173/details
>
> It says
>
> --8<---------------cut
> here---------------start------------->8---
> Status Failed (dependency)
> --8<---------------cut
> here---------------end--------------->8---
Cuirass should link to the failing dependencies for further
inspection, but doesn't (yet?). You have to guess. It's fun.
> and does not have any logs.
Since these builds were never attempted, they never produced any
logs. I think that's the correct approach.
This is also why blindly raising time-outs for these packages
isn't the solution: there's nothing to time out.
> Something is fishy.
Not fishy, just -ETODO.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-03-03 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 14:58 Missing substitutes and TIMEOUT property (Racket, MAME) Pierre Neidhardt
2020-03-02 11:50 ` Pierre Neidhardt
2020-03-02 17:29 ` Leo Famulari
2020-03-03 9:42 ` Pierre Neidhardt
2020-03-03 13:48 ` Tobias Geerinckx-Rice [this message]
2020-03-03 14:09 ` Pierre Neidhardt
2020-03-03 14:35 ` Tobias Geerinckx-Rice
2020-03-03 17:01 ` Gábor Boskovits
2020-03-04 14:17 ` Pierre Neidhardt
2020-03-12 13:26 ` Ludovic Courtès
2020-03-12 13:45 ` Pierre Neidhardt
2020-03-15 16:52 ` Marius Bakke
2020-03-15 21: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv354kil.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.