bug#32575: [Cuirass] Filter results by architecture

2021-03-25 Thread Mathieu Othacehe
Hello, The Builds table now has as "system" field on Cuirass master. The job system is displayed on http://ci.guix.gnu.org/eval/xxx page. With 1ed93601089e774df849bc4ffab718bb1f142d34 it is also possible to sort by table columns, including the "System" column. Closing this one, Thanks, Mathie

bug#32575: [Cuirass] Filter results by architecture

2018-08-31 Thread Ricardo Wurmus
Hi Joshua, > 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 is >> impossible to tell, how each of the supported architectures is affected. >> >> It would be good if we cou

bug#32575: [Cuirass] Filter results by architecture

2018-08-31 Thread Clément Lassieur
Ludovic Courtès writes: >> CREATE TABLE Builds ( >> derivationTEXT NOT NULL PRIMARY KEY, >> evaluationINTEGER NOT NULL, >> job_name TEXT NOT NULL, >> systemTEXT NOT NULL, >> nix_name TEXT NOT NULL, >> log TEXT NOT NULL, >> statusINTEGER NO

bug#32575: [Cuirass] Filter results by architecture

2018-08-30 Thread Ludovic Courtès
Clément Lassieur skribis: > Ludovic Courtès writes: [...] >> Perhaps what we would need is to internally change how jobs are >> represented in the database: we could have one job, “hello”, connected >> to one or more “builds”, each with its own system. >> >> I think it would amount to splittin

bug#32575: [Cuirass] Filter results by architecture

2018-08-30 Thread Clément Lassieur
Ludovic Courtès writes: > Hi Danny & all, > > Danny Milosavljevic skribis: > >> I think that for a portable package, the architecture it runs on is >> an implementation detail - it should build on all of them. If it doesn't, >> that should show up as an error. >> >> So I had >> >> hello

bug#32575: [Cuirass] Filter results by architecture

2018-08-30 Thread Ludovic Courtès
Hi Danny & all, Danny Milosavljevic skribis: > I think that for a portable package, the architecture it runs on is > an implementation detail - it should build on all of them. If it doesn't, > that should show up as an error. > > So I had > > hello [x86_64-checkbox-log] [armhf-checkbox-l

bug#32575: [Cuirass] Filter results by architecture

2018-08-30 Thread Danny Milosavljevic
Hi Ricardo, On Wed, 29 Aug 2018 15:54:47 +0200 Ricardo Wurmus wrote: > 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. > >

bug#32575: [Cuirass] Filter results by architecture

2018-08-29 Thread Gábor Boskovits
Joshua Branson ezt írta (időpont: 2018. aug. 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 is > > impossible to tell, how each of the supported archi

bug#32575: [Cuirass] Filter results by architecture

2018-08-29 Thread Joshua Branson
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 is > impossible to tell, how each of the supported architectures is affected. > > It would be good if we could separate the view b

bug#32575: [Cuirass] Filter results by architecture

2018-08-29 Thread Ricardo Wurmus
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 mor