summaryrefslogtreecommitdiff
path: root/.github/workflows/macos_unit_tests.yaml
diff options
context:
space:
mode:
authorScott Wittenburg <scott.wittenburg@kitware.com>2020-10-02 15:37:47 -0600
committerGitHub <noreply@github.com>2020-10-02 15:37:47 -0600
commit7cfdf61979bdabb15cfeedb2b505b7ef3725bf28 (patch)
tree1db31c325ea628b3d738efd89b38723f919c28db /.github/workflows/macos_unit_tests.yaml
parent670f3a5e4cf1e6a5878b1fb311a3663434daf92a (diff)
downloadspack-7cfdf61979bdabb15cfeedb2b505b7ef3725bf28.tar.gz
spack-7cfdf61979bdabb15cfeedb2b505b7ef3725bf28.tar.bz2
spack-7cfdf61979bdabb15cfeedb2b505b7ef3725bf28.tar.xz
spack-7cfdf61979bdabb15cfeedb2b505b7ef3725bf28.zip
Fix location in spec.yaml where we look for full_hash (#19132)
When we attempt to determine whether a remote spec (in a binary mirror) is up-to-date or needs to be rebuilt, we compare the full_hash stored in the remote spec.yaml file against the full_hash computed from the local concrete spec. Since the full_hash moved into the spec (and is no longer at the top level of the spec.yaml), we need to look there for it. This oversight from #18359 was causing all specs to get rebuilt when the full_hash wasn't fouhd at the expected location.
Diffstat (limited to '.github/workflows/macos_unit_tests.yaml')
0 files changed, 0 insertions, 0 deletions