From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel@gnu.org, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Cuirass job names and package variants
Date: Fri, 25 Jun 2021 16:30:45 +0200 [thread overview]
Message-ID: <87tulm2ezu.fsf@inria.fr> (raw)
In-Reply-To: <ad85d8e07bd16fa8905f3b2d286b582b193cbdca.camel@student.tugraz.at> (Leo Prikler's message of "Fri, 25 Jun 2021 14:12:54 +0200")
Leo Prikler <leo.prikler@student.tugraz.at> skribis:
> Am Freitag, den 25.06.2021, 13:44 +0200 schrieb Ludovic Courtès:
[...]
>> However, variants of a given package have the same package
>> name/version,
>> and thus the same job name. Apparently Cuirass only takes the first
>> job
>> with a given name into account and dismisses subsequent ones.
>>
>> What would be a good way to address this, either in Cuirass or in the
>> user config?
> Do we already know – or could we compute – store paths at this point in
> time? It seems as though this could be solved once more by assigning
> ids based on hashed inputs. So each job-name would be something like
> (package-name)-(package-version)-(first-bytes-of-package-input-hash).
> WDYT?
That job names are human-readable is a feature. :-)
However, what we could do is have an autoincrement ID or similar (?)
rather than the package name used as the actual key. Dunno.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-06-25 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 11:44 Cuirass job names and package variants Ludovic Courtès
2021-06-25 12:12 ` Leo Prikler
2021-06-25 14:30 ` Ludovic Courtès [this message]
2021-06-25 14:41 ` Leo Prikler
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=87tulm2ezu.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=othacehe@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).