all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Missing substitutes and TIMEOUT property (Racket, MAME)
Date: Tue, 3 Mar 2020 18:01:15 +0100	[thread overview]
Message-ID: <CAE4v=pjgG7vqcry_cVHs0HRHyRisZ=StUcyW5Fe=Tit84Jz+2A@mail.gmail.com> (raw)
In-Reply-To: <87sgip4ibr.fsf@nckx>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

Hello Tobias,

Tobias Geerinckx-Rice <me@tobias.gr> ezt írta (időpont: 2020. márc. 3., Ke
15:35):

> Tobias Geerinckx-Rice 写道:
> > Since these builds were never attempted, they never produced any
> > logs.
>
> Not the same architecture, but here's a staging MAME that was
> built and killed without explanation after a non-magical-looking
> number of seconds:
>
> http://ci.guix.gnu.org/build/2337230/details
>
> I don't understand.  There has to be a better way to query Cuirass
> than endlessly clicking ‘Next’…  :-
>
You can try to get failing dependency information from the guix data
service. Last time I checked that did work. It should list all the failed
dependencies that failed directly.

>
> T G-R
>

[-- Attachment #2: Type: text/html, Size: 1348 bytes --]

  reply	other threads:[~2020-03-03 17:01 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
2020-03-03 14:09       ` Pierre Neidhardt
2020-03-03 14:35       ` Tobias Geerinckx-Rice
2020-03-03 17:01         ` Gábor Boskovits [this message]
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='CAE4v=pjgG7vqcry_cVHs0HRHyRisZ=StUcyW5Fe=Tit84Jz+2A@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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.