unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Joshua Branson <jbranso@fastmail.com>
Cc: 32575@debbugs.gnu.org
Subject: bug#32575: [Cuirass] Filter results by architecture
Date: Thu, 30 Aug 2018 07:56:26 +0200	[thread overview]
Message-ID: <CAE4v=pgmEZvYFcKoNpucpcB8iJu+FrM+983Tth4YPyCKcHxNMA@mail.gmail.com> (raw)
In-Reply-To: <877ek8dhkm.fsf@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]

Joshua Branson <jbranso@fastmail.com> ezt írta (időpont: 2018. aug. 29.,
Sze, 22:41):

> Ricardo Wurmus <rekado@elephly.net> writes:
>
> > The Cuirass web interface shows the number of successful, failed, and
> > pending builds for each evaluation.  Looking at just these numbers it is
> > impossible to tell, how each of the supported architectures is affected.
> >
> > It would be good if we could separate the view by architecture.  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.
> >
> >     http://ci.guix.info/jobset/guix-master?system=x86_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
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2265 bytes --]

  reply	other threads:[~2018-08-30  6:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 13:54 bug#32575: [Cuirass] Filter results by architecture Ricardo Wurmus
2018-08-29 20:49 ` Joshua Branson
2018-08-30  5:56   ` Gábor Boskovits [this message]
2018-08-30  8:09   ` Ricardo Wurmus
2018-08-30  9:41 ` Danny Milosavljevic
2018-08-30 12:14   ` Ludovic Courtès
2018-08-30 12:50     ` Clément Lassieur
2018-08-30 20:33       ` Ludovic Courtès
2018-08-31 18:35         ` Clément Lassieur
2021-03-25 13:32           ` Mathieu Othacehe

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='CAE4v=pgmEZvYFcKoNpucpcB8iJu+FrM+983Tth4YPyCKcHxNMA@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=32575@debbugs.gnu.org \
    --cc=jbranso@fastmail.com \
    /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).