unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Cuirass enhancements
Date: Wed, 19 Jun 2019 15:55:03 +0200	[thread overview]
Message-ID: <87sgs5n0i5.fsf@elephly.net> (raw)
In-Reply-To: <20190618195025.62b32955@alma-ubu>


Björn Höfling <bjoern.hoefling@bjoernhoefling.de> writes:

> * If a job failed because of its dependency, I would like to see which
> one caused the problem. I don't know how to find that out.
> In Hydra, the name and build log of the failing dependency was directly
> available.

This is now implemented on the “details” page.  The logs of the failed
prerequisites are linked directly.

(We don’t keep that kind of information in the database, so we don’t
know what *build* relates to the failure.  We get that information in a
round-about way through the derivation of the build and the Guix
derivations API.)

--
Ricardo

  parent reply	other threads:[~2019-06-19 13:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 17:50 Cuirass enhancements Björn Höfling
2019-06-18 20:52 ` Ricardo Wurmus
2019-06-18 22:19 ` Ricardo Wurmus
2019-06-19  7:49 ` Ricardo Wurmus
2019-06-19  8:23   ` Ricardo Wurmus
2019-06-19 10:16     ` Björn Höfling
2019-06-19 13:45 ` Ricardo Wurmus
2019-06-19 13:55 ` Ricardo Wurmus [this message]
2019-06-19 16:07 ` Danny Milosavljevic
2019-06-19 19:49   ` Ricardo Wurmus
2019-06-23 22:08     ` Björn Höfling
2019-06-21 15:18 ` Ludovic Courtès
2019-06-23 22:02   ` Björn Höfling

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=87sgs5n0i5.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@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).