GNU bug report logs - #38550
Cuirass: in job-name: replace 'version' with 'anchor'

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Clément Lassieur <clement <at> lassieur.org>
Subject: bug#38550: closed (Re: bug#38550: Cuirass: in job-name: replace
 'version' with 'anchor')
Date: Thu, 25 Mar 2021 14:00:01 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#38550: Cuirass: in job-name: replace 'version' with 'anchor'

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 38550 <at> debbugs.gnu.org.

-- 
38550: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38550
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mathieu Othacehe <othacehe <at> gnu.org>
To: Clément Lassieur <clement <at> lassieur.org>
Cc: 38550-done <at> debbugs.gnu.org
Subject: Re: bug#38550: Cuirass: in job-name: replace 'version' with 'anchor'
Date: Thu, 25 Mar 2021 14:59:19 +0100

Hello Clément,

It is possible to search for the last build of a given job using the Web
interface search form.

For example,
http://ci.guix.gnu.org/search?query=spec%3Aguix-master+gajim

which corresponds to the search "spec:guix-master gajim", will show the
last build job for gajim on master. A build job history is also
displayed on the build details page.

Closing this one,

Thanks,

Mathieu

[Message part 3 (message/rfc822, inline)]

From: Clément Lassieur <clement <at> lassieur.org>
To: bug-guix <at> gnu.org
Subject: Cuirass: in job-name: replace 'version' with 'anchor'
Date: Mon, 09 Dec 2019 18:24:57 +0100

See IRC conversation[1].  The idea is that we want to be able to select
all the builds that have the same job-name.  Then we'll be able to see
the first one that's failing and its associated evaluation (the
culprit).

We could use PACKAGES->ANCHORS[2], which was created for the website.
Thus instead of having

 gajim-1.1.3.x86-64-linux <-fails gcc-7.4.x86_64-linux gcc-6.5.x86_64-linux
 gajim-1.1.3.x86-64-linux <-fails gcc-7.4.x86_64-linux gcc-6.5.x86_64-linux
 gajim-1.1.2.x86-64-linux <-fails gcc-7.3.x86_64-linux gcc-6.4.x86_64-linux
 gajim-1.1.2.x86-64-linux <-OK    gcc-7.3.x86_64-linux gcc-6.4.x86_64-linux

We'd have

 gajim.x86-64-linux <-fails       gcc.x86_64-linux     gcc-6.5.x86_64-linux
 gajim.x86-64-linux <-fails       gcc.x86_64-linux     gcc-6.5.x86_64-linux
 gajim.x86-64-linux <-fails       gcc.x86_64-linux     gcc-6.4.x86_64-linux
 gajim.x86-64-linux <-OK          gcc.x86_64-linux     gcc-6.4.x86_64-linux

And we could track the first failing Gajim (or GCC).

Each of the above column really represents a package definition tracked
in time.  GCC 7 and GCC 6 are two different packages at a given moment
in time, so they should have different job names.

Note that it doesn't work with packages for which we keep an old version
around if that version changes (e.g. from GCC 6.4 to GCC 6.5 in my
example).  But I imagine it's pretty rare.  Don't know.

This work is to be done in (gnu ci).

Comments welcome :)

Clément

[1]: http://logs.guix.gnu.org/guix/2019-12-09.log#171227
[2]: https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/commit/?id=497145ef95cfc7548eb7c406d6227104f4b66700

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.