Closed
Conversation
tldahlgren
added
WIP
bugfix
tldahlgren
added a commit
to tldahlgren/spack
that referenced
this pull request
Oct 22, 2019
Contributor
Author
|
The lock and corresponding database test fixes are done in #13441 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #8772
When chaining Spack installations, the upstream Spack instance is not supposed to be locked; however, that is not currently the case.
This PR ensures the
ForbiddenLockis retained for upstream databases and associated operations do not attempt to acquire read locks.TODO: