Spack build failing about norse

[muffgaga]

Hmm, I initially thought that this is related to some changed variant settings in upstream spack (we use the latest release… so maybe something changed) — but all options are still there… so maybe it's the combination.
Regarding bumping the version → norse uses depends_on("[email protected]:", type=("build", "run")) which means "everything >= 1.9.0"…
I try to reproduce locally.

[muffgaga]

Looks like we disable cuda and cudnn — but the latter can't be disabled if cuda is already disabled ;)… see #333

Upstream definition of this variant can be found here (the when='+cuda' disables this variant completely if cuda is gone).
This "conditional variant" was introduced for py-torch in spack upstream in py-torch: use conditional variants.

[muffgaga]

Ok, my first commit #333 would have fixed https://github.com/norse/norse/runs/6843260254?check_suite_focus=true#step:4:363 but not the errors in subsequent builds — maybe this is related to the ARCH variable setting a specific processor architecture for spack… jap, looks like it — https://github.com/norse/norse/runs/7045092304?check_suite_focus=true started building norse again (i.e. concretization of the dependencies worked). However, this now rebuilds all the dependencies before building norse → this will take a while (maybe we also need some retries to fill the cache with package build files). Maybe related to some machine config change (as the spack version didn't change since end of May) yielding a change in what spack determines as ARCH… our setting of ARCH in the build script does not match the machine anymore → spack can't find the system compiler anymore.