Force reinstall pytest during installation into monolithic CASA in case the pytest delivered is already up-to-date#118
Open
psheehan wants to merge 1 commit into
Conversation
…se the pytest delivered is already up-to-date
|
Codecov Report❌ Patch coverage is
🚀 New features to boost your workflow:
|
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.
Using pytest within monolithic CASA requires replacing the version delivered with monolithic CASA. This is handled under-the-hood in the
auto_selfcal.setup_monolithic_CASAfunction, but right now uses only--upgrade, assuming that the pytest version is out of date. If the pytest delivered with monolithic CASA is up-to-date, this will do nothing, and pytest remains broken. To remedy this, this PR adds the--force-reinstallflag to force pytest to be reinstalled, even if it is up-to-date already.