From: Roel Janssen <roel@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>, guix-devel@gnu.org
Subject: Re: List of failing packages
Date: Mon, 04 Nov 2019 15:23:02 +0100 [thread overview]
Message-ID: <d2d863caef20b5fb3e1161ea52bcea85da7dd28b.camel@gnu.org> (raw)
In-Reply-To: <05DEF5E9-ADE1-4C13-B24D-C2BA5675F43E@lepiller.eu>
On Mon, 2019-11-04 at 14:51 +0100, Julien Lepiller wrote:
> Le 4 novembre 2019 13:28:57 GMT+01:00, Roel Janssen <roel@gnu.org> a
> écrit :
> > Dear Guix,
> >
> > I'm trying to contribute to GNU Guix again, and I'd like to see if
> > I
> > can solve build failures to make for a more stable Guix. It would
> > be
> > very convenient to have a list of packages that are currently
> > failing
> > to build, and perhaps also some history on it (how many times did
> > the
> > build fail, and since when does it fail).
> >
> > Does such a list exist, and if so, where can I find it?
> >
> > Kind regards,
> > Roel Janssen
>
> I think you'ne looking for https://ci.guix.gnu.org. look for
> evaluations of guix master, and their failures. You can also look for
> evaluations of a package with the search bar at the top right.
But is there a list of *all packages that fail ot build*?
So, not only just a single evaluation like:
https://ci.guix.gnu.org/eval/8538?status=failed
But a list of ~11000 packages and their build status (like Hydra
showed). With Hydra, when clicking on a failed build you could see
previous builds of that same package and its success or failure of
them. I found that very useful.
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2019-11-04 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 12:28 List of failing packages Roel Janssen
2019-11-04 13:51 ` Julien Lepiller
2019-11-04 14:23 ` Roel Janssen [this message]
2019-11-04 15:26 ` Ricardo Wurmus
2019-11-05 8:24 ` Help on search (was: List of failing packages) Hartmut Goebel
2019-12-19 10:35 ` Documenting Cuirass features " Clément Lassieur
2019-12-19 10:59 ` Pierre Neidhardt
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=d2d863caef20b5fb3e1161ea52bcea85da7dd28b.camel@gnu.org \
--to=roel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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).