diff options
author | Stephen Sachs <stesachs@amazon.com> | 2023-05-24 15:55:00 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-05-24 06:55:00 -0700 |
commit | 2d77e44f6f57dcd1529c1ce712acfc6a60f47206 (patch) | |
tree | 9242d604bf51d539195891fddd8c2d6ad101ec63 /CITATION.cff | |
parent | 033599c4cd0889af2cb8ae4b52984fa88558f5c2 (diff) | |
download | spack-2d77e44f6f57dcd1529c1ce712acfc6a60f47206.tar.gz spack-2d77e44f6f57dcd1529c1ce712acfc6a60f47206.tar.bz2 spack-2d77e44f6f57dcd1529c1ce712acfc6a60f47206.tar.xz spack-2d77e44f6f57dcd1529c1ce712acfc6a60f47206.zip |
Pcluster local buildcache (#37852)
* [pcluster pipeline] Use local buildcache instead of upstream spack
Spack currently does not relocate compiler references from upstream spack
installations. When using a buildcache we don't need an upstream spack.
* gcc needs to be installed via postinstall to get correct deps
* quantum-espresso@gcc@12.3.0 returns ICE on neoverse_{n,v}1
* Force gitlab to pull the new container
* Revert "Force gitlab to pull the new container"
This reverts commit 3af5f4cd88245138992deb2a46c17e6f85858d68.
Seems the gitlab version does not yet support "pull_policy" in .gitlab-ci.yml
* Gitlab keeps picking up wrong container. Renaming
* Update containers once more after failed build
Diffstat (limited to 'CITATION.cff')
0 files changed, 0 insertions, 0 deletions