From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: ci wishlist
Date: Wed, 31 Jul 2019 17:31:10 +0200
Message-ID: <87o91ate4h.fsf@elephly.net>
References: <2D8224C5-876A-4EAF-A3C3-C3AC36B8D139@vllmrt.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:57144)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <rekado@elephly.net>) id 1hsqZV-00033G-W8
 for guix-devel@gnu.org; Wed, 31 Jul 2019 11:31:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <rekado@elephly.net>) id 1hsqZV-0008I1-1Y
 for guix-devel@gnu.org; Wed, 31 Jul 2019 11:31:21 -0400
Received: from sender-of-o51.zoho.com ([135.84.80.216]:21294)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <rekado@elephly.net>) id 1hsqZQ-0008E9-6g
 for guix-devel@gnu.org; Wed, 31 Jul 2019 11:31:16 -0400
In-reply-to: <2D8224C5-876A-4EAF-A3C3-C3AC36B8D139@vllmrt.net>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: guix-devel@gnu.org


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=
=E2=80=99t
>   have a successful build anytime later)

We can seach packages and restrict them by =E2=80=9Cspec=E2=80=9D and/or =
=E2=80=9Csystem=E2=80=9D and
that can give you a list of other builds.  It=E2=80=99s not quite what you=
=E2=80=99re
looking for, but it can get close enough.

> - on a given branch, which broken packages are also broken on master?

I=E2=80=99d like to see something like that as well.  Would make it much ea=
sier
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=E2=
=80=99t
all that helpful, because I don=E2=80=99t know if that=E2=80=99s my fault o=
r if these
failures are =E2=80=9Cexpected=E2=80=9D.)

--=20
Ricardo