You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3576740
Browse filesBrowse the repository at this point in the historyBrowse files
fix(gap): choose the bump source by toolchain family and generation
For a no-recipe row, stack gap names the newest easyconfig of the name
on any toolchain as the bump source. Between builds of the newest
version the file name decided, so an upper-case toolchain name sorted
first and an older toolchain before a newer one: QuantumESPRESSO 7.5 was
bumped from NVHPC-25.3-CUDA-12.8.0 rather than foss-2025b, and Bandage
0.9.0 from GCCcore-11.3.0 rather than GCCcore-14.3.0.
Between builds of one version the bump source is now one on a toolchain
family the generation uses, then the one on the newest toolchain
generation, as data/eessi-generations.toml and the shipped hierarchies
place it, then the newest toolchain of one name. Versions of two
toolchain names are not compared. The recipe route keeps its order.
On the EESSI 2026.06 site list from the deck demo, 120 of 249 no-recipe
rows change bump source, each to a build from a newer toolchain
generation; recipe.tsv and roots.txt are unchanged. Unit tests in gap.rs
cover the family, the generation, and the family match; the first two
fail without the fix.
`stack gap` picks the bump source of a `no-recipe` row among builds of the newest version by toolchain family and generation instead of file name: a build on a toolchain family of the generation comes first, then the newest toolchain generation, so QuantumESPRESSO 7.5 is bumped from `foss-2025b` rather than `NVHPC-25.3-CUDA-12.8.0`, and a recipe on `GCCcore-14.3.0` is preferred to one on `GCCcore-11.3.0`.
0 commit comments