Ensure setuptools and wheel are installed & up-to-date in CI unit tests #573
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #573 +/- ##
=======================================
Coverage 99.47% 99.47%
=======================================
Files 84 84
Lines 5568 5568
=======================================
Hits 5539 5539
Misses 29 29 Continue to review full report at Codecov.
|
|
Kudos, SonarCloud Quality Gate passed!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
wheelpackage has not been available for dependency installations for unit tests in GH Actions runs. There has been messages likeUsing legacy 'setup.py install' for pyrsistent, since package 'wheel' is not installed.Installing
wheelgets rid of the messages, possibly also making dependency installations faster.This PR also makes sure
setuptoolsis updated, making dependency installation environment the same as in building Dockerfile.This issue came into attention via a comment in #572.