stackinator
stackinator copied to clipboard
eth-cscs
As pointed out by @albestro. from spack changelog (https://github.com/spack/spack/blob/develop/CHANGELOG.md#L313) ``` buildcache push: make `--allow-root` the default and deprecate the option (#38878) ``` It was announced to remove `--allow-root` in spack...
When loading a default view via `uenv` from an image built with `stackinator`, only `/user-environment/env/default/lib` is added to `LD_LIBRARY_FLAGS`. We should also add `lib64` to `LD_LIBRARY_PATH` as well.
https://github.com/eth-cscs/stackinator/blob/5f161107f51c8ff9c1cf8989e9f5ccb5e0d7ba65/docs/configuring.md?plain=1#L45-L51 In addition to the repeated "the following", IMHO the bullet points list is not straightforward to understand. Some doubts I have: - it probably refers to `spack env activate...
- Avoid concertizing `cray-mpich` with unsupported compilers such as `clang`. - Make sure the dependencies (gtl, pals) use the same compiler as `cray-mpich`
When running a uenv and use it as spack upstream via `spack -C /user-environment`, spack spec on santis may pickup `cray-mpich+rocm`. TODO: Add the required bits to `/user-environment/config/packages.yaml` to obtain...
The documentation states that > A build cache can be configured to be read-only by not providing a key in the cache configuration file. However, not providing a key results...
When the version of gcc in the gcc compiler toolchain matches the system-provided compiler, the compiler is not found when generating `compilers.yaml` for any spack environment that requests the gcc...
`stack-config` will error when the target recipe has a repo with `/packages/cray-mpich`. This appears to be because the alps repo is always added, regardless of the `-r` argument?
The `recipe` fixture could be parametrised, instead of returning a list of recipes to loop over in other test functions. https://github.com/eth-cscs/stackinator/blob/dbd21f12d58d1511cdcac6eb927f8cd73e371568/unittests/test_schema.py#L26-L28