From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor?= Boskovits Subject: bug#32575: [Cuirass] Filter results by architecture Date: Thu, 30 Aug 2018 07:56:26 +0200 Message-ID: References: <87a7p5b7x3.fsf@elephly.net> <877ek8dhkm.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f5887b0574a0bc6f" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39338) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvG2g-00040f-FH for bug-guix@gnu.org; Thu, 30 Aug 2018 02:02:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvFx0-0005mW-GF for bug-guix@gnu.org; Thu, 30 Aug 2018 01:57:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:32793) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fvFx0-0005mK-BZ for bug-guix@gnu.org; Thu, 30 Aug 2018 01:57:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fvFx0-0007Zc-3q for bug-guix@gnu.org; Thu, 30 Aug 2018 01:57:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <877ek8dhkm.fsf@fastmail.com> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Joshua Branson Cc: 32575@debbugs.gnu.org --000000000000f5887b0574a0bc6f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Joshua Branson ezt =C3=ADrta (id=C5=91pont: 2018. au= g. 29., Sze, 22:41): > Ricardo Wurmus writes: > > > The Cuirass web interface shows the number of successful, failed, and > > pending builds for each evaluation. Looking at just these numbers it i= s > > impossible to tell, how each of the supported architectures is affected= . > > > > It would be good if we could separate the view by architecture. Then w= e > > could more easily determine that a change broke many builds for one > > architecture while fixing builds on another. > > > > One way to do this would be to accept an optional query variable, e.g. > > > > http://ci.guix.info/jobset/guix-master?system=3Dx86_64-linux > > That is an option. Another one is using a REST API. It seems to have > all the hype these days. So the URL would turn into: > > http://ci.guix.info/jobset/guix-master/system/x86_64-linux > > Though I freely admit, I don't completely understand the benefits of REST= . > > Actually there are some more options to do this, but I think this should go with a more generic filtering/sorting capability, using a uniform implementation. I noticed this in a writeup before, Ludo asked me to turn that to a TODO on the Cuirass repository, and I will do that once back from vacation. > > > > This could be selected from a drop-down on the page or exposed through = a > > number of links. > > > > -- > > Ricardo > > > > --000000000000f5887b0574a0bc6f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Joshua Branson= <jbranso@fastmail.com> e= zt =C3=ADrta (id=C5=91pont: 2018. aug. 29., Sze, 22:41):
Ricardo Wurmus <rekado@elephly.net> writes:

> The Cuirass web interface shows the number of successful, failed, and<= br> > pending builds for each evaluation.=C2=A0 Looking at just these number= s it is
> impossible to tell, how each of the supported architectures is affecte= d.
>
> It would be good if we could separate the view by architecture.=C2=A0 = Then we
> could more easily determine that a change broke many builds for one > architecture while fixing builds on another.
>
> One way to do this would be to accept an optional query variable, e.g.=
>
>=C2=A0 =C2=A0 =C2=A0http://ci.guix.i= nfo/jobset/guix-master?system=3Dx86_64-linux

That is an option.=C2=A0 Another one is using a REST API.=C2=A0 It seems to= have
all the hype these days.=C2=A0 So the URL would turn into:

=C2=A0 =C2=A0 =C2=A0http://ci.guix.info/jo= bset/guix-master/system/x86_64-linux

Though I freely admit, I don't completely understand the benefits of RE= ST.

Actually there are some more options to do this, but = I think this should go with
a more generic filtering/sorting capa= bility, using a uniform implementation. I
noticed this in a write= up before, Ludo asked me to turn that to a TODO on
the Cuirass re= pository, and I will do that once back from vacation.=C2=A0
>
> This could be selected from a drop-down on the page or exposed through= a
> number of links.
>
> --
> Ricardo



--000000000000f5887b0574a0bc6f--