summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorScott Wittenburg <scott.wittenburg@kitware.com>2022-10-20 10:33:18 -0600
committerGitHub <noreply@github.com>2022-10-20 10:33:18 -0600
commit9a1957c881dad228eb875ac0e65e3a085f4acb25 (patch)
tree02181d12ce937febfe8b84674f3a7cfe3079e2f1 /README.md
parentaf5d6295d58d1f44c7ce9d6ccc92cf6004e8eae6 (diff)
downloadspack-9a1957c881dad228eb875ac0e65e3a085f4acb25.tar.gz
spack-9a1957c881dad228eb875ac0e65e3a085f4acb25.tar.bz2
spack-9a1957c881dad228eb875ac0e65e3a085f4acb25.tar.xz
spack-9a1957c881dad228eb875ac0e65e3a085f4acb25.zip
gitlab: Do not use root_spec['pkg_name'] anymore (#33403)
* gitlab: Do not use root_spec['pkg_name'] anymore For a long time it was fine to index a concrete root spec with the name of a dependency in order to access the concrete dependency spec. Since pipelines started using `--use-buildcache dependencies:only,package:never` though, it has exposed a scheduling issue in how pipelines are generated. If a concrete root spec depends on two different hashes of `openssl` for example, indexing that root with just the package name is ambiguous, so we should no longer depend on that approach when scheduling jobs. * env: make sure exactly one spec in env matches hash
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions