From: "Clément Lassieur" <clement@lassieur.org>
To: 38550@debbugs.gnu.org
Subject: bug#38550: Cuirass: in job-name: replace 'version' with 'anchor'
Date: Mon, 09 Dec 2019 18:24:57 +0100 [thread overview]
Message-ID: <87muc1l8d2.fsf@lassieur.org> (raw)
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
next reply other threads:[~2019-12-09 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 17:24 Clément Lassieur [this message]
2021-03-25 13:59 ` bug#38550: Cuirass: in job-name: replace 'version' with 'anchor' 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=87muc1l8d2.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=38550@debbugs.gnu.org \
/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).