From: Ricardo Wurmus <rekado@elephly.net>
To: Robert Vollmert <rob@vllmrt.net>
Cc: guix-devel@gnu.org
Subject: Re: ci wishlist
Date: Wed, 31 Jul 2019 17:31:10 +0200 [thread overview]
Message-ID: <87o91ate4h.fsf@elephly.net> (raw)
In-Reply-To: <2D8224C5-876A-4EAF-A3C3-C3AC36B8D139@vllmrt.net>
Robert Vollmert <rob@vllmrt.net> writes:
> some questions that the ci interface should answer, but makes quite hard:
>
> - on a given branch, which packages are broken? (the answer seems to be:
> all packages that have a failed build in some evaluation and that don’t
> have a successful build anytime later)
We can seach packages and restrict them by “spec” and/or “system” and
that can give you a list of other builds. It’s not quite what you’re
looking for, but it can get close enough.
> - on a given branch, which broken packages are also broken on master?
I’d like to see something like that as well. Would make it much easier
to see what packages are *newly* failing, presumably because of a change
on this branch.
(Right now the list of failed builds for wip-texlive, for example, isn’t
all that helpful, because I don’t know if that’s my fault or if these
failures are “expected”.)
--
Ricardo
prev parent reply other threads:[~2019-07-31 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 14:49 ci wishlist Robert Vollmert
2019-07-31 15:31 ` Ricardo Wurmus [this message]
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=87o91ate4h.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=rob@vllmrt.net \
/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.