summaryrefslogtreecommitdiff
path: root/.github/workflows/setup_git.sh
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2022-10-21 14:42:06 +0200
committerGitHub <noreply@github.com>2022-10-21 14:42:06 +0200
commitb1559cc831620ee2b2cf8e57fdecc5bb3bf8edfd (patch)
tree74bca487f76ef38914b29e1016f8fb016216ad7b /.github/workflows/setup_git.sh
parent93db654b8de6ae76bef382dc3c37eb715baa68b5 (diff)
downloadspack-b1559cc831620ee2b2cf8e57fdecc5bb3bf8edfd.tar.gz
spack-b1559cc831620ee2b2cf8e57fdecc5bb3bf8edfd.tar.bz2
spack-b1559cc831620ee2b2cf8e57fdecc5bb3bf8edfd.tar.xz
spack-b1559cc831620ee2b2cf8e57fdecc5bb3bf8edfd.zip
gitlab: when_possible -> false (#33443)
`reuse` and `when_possible` concretization broke the invariant that `spec[pkg_name]` has unique keys. This invariant is relied on in tons of places, such as when setting up the build environment. When using `when_possible` concretization, one may end up with two or more `perl`s or `python`s among the transitive deps of a spec, because concretization does not consider build-only deps of reusable specs. Until the code base is fixed not to rely on this broken property of `__getitem__`, we should disable reuse in CI.
Diffstat (limited to '.github/workflows/setup_git.sh')
0 files changed, 0 insertions, 0 deletions