[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cuirass job names and package variants
From: |
Leo Prikler |
Subject: |
Re: Cuirass job names and package variants |
Date: |
Fri, 25 Jun 2021 14:12:54 +0200 |
User-agent: |
Evolution 3.34.2 |
Am Freitag, den 25.06.2021, 13:44 +0200 schrieb Ludovic Courtès:
> Hello!
>
> Cuirass support in (gnu ci) computes job names as a function of
> package
> names (the ‘job-name’ procedure). I wanted to build several package
> variants using ‘--with-input’, which I expressed in a manifest:
>
>
> https://gitlab.inria.fr/guix-hpc/guix-hpc/-/blob/master/manifest#L33-50
>
> 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?