Re: branch master updated: ci: Add bootstrap packages to the core subset.

2021-07-25 Thread Ludovic Courtès
Hi,

Mathieu Othacehe  skribis:

>> Should we arrange so that jobs for the commencement.scm packages get a
>> custom name, for example prefixed by “commencement.”?
>
> The primary key for the Builds table is on the derivation field, so
> duplicated job-name shouldn't be an issue. If you search for
> "gcc-toolchain.aarch64-linux" here:
> https://ci.guix.gnu.org/eval/59586?paginate=0, you will find 9
> occurrences.
>
> Did you find a specific job missing in that evaluation?
>
> I'll see if I can reproduce the issue you are describing here:
> https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00222.html.

Actually, looking at the dashboard at
, I see that the
variants defined in the manifest are all there, so we’re fine.

Sorry for the confusion!

Ludo’.



Re: branch master updated: ci: Add bootstrap packages to the core subset.

2021-07-10 Thread Mathieu Othacehe


Hey Ludo!

> Should we arrange so that jobs for the commencement.scm packages get a
> custom name, for example prefixed by “commencement.”?

The primary key for the Builds table is on the derivation field, so
duplicated job-name shouldn't be an issue. If you search for
"gcc-toolchain.aarch64-linux" here:
https://ci.guix.gnu.org/eval/59586?paginate=0, you will find 9
occurrences.

Did you find a specific job missing in that evaluation?

I'll see if I can reproduce the issue you are describing here:
https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00222.html.

Thanks,

Mathieu



Re: branch master updated: ci: Add bootstrap packages to the core subset.

2021-07-10 Thread Ludovic Courtès
Hi Mathieu!

guix-comm...@gnu.org skribis:

> commit 37861f6c293d7ed1033050b2b0597885ba65186f
> Author: Mathieu Othacehe 
> AuthorDate: Fri Jul 9 12:07:24 2021 +0200
>
> ci: Add bootstrap packages to the core subset.
> 
> * gnu/ci.scm (%bootstrap-packages): New variable.
> (cuirass-jobs): Add it to the core subset.

[...]

> +(define %bootstrap-packages
> +  ;; Return the list of bootstrap packages from the commencement module.
> +  (filter package?
> +  (module-map
> +   (lambda (sym var)
> + (variable-ref var))
> +   (resolve-module '(gnu packages commencement)
> +
>  (define (packages-to-cross-build target)
>"Return the list of packages to cross-build for TARGET."
>;; Don't cross-build the bootstrap tarballs for MinGW.
> @@ -508,7 +517,7 @@ valid."
> (map (lambda (package)
>(package-job store (job-name package)
> package system))
> -%core-packages)
> +(append %bootstrap-packages %core-packages))

I believe the effect is that the same-named packages, those not in
commencement.scm, are no longer being built, as discussed here:

  https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00222.html

Should we arrange so that jobs for the commencement.scm packages get a
custom name, for example prefixed by “commencement.”?

Thanks,
Ludo’.