Pin tox version in CI #9460
Merged
Pin tox version in CI #9460
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
THe most recent release tox, 4.4.0, changed the behavior of how tox interacts with constraints files. It is raising an error because it doesn't like the format of our constraints file in qiskit. This commit works around this by pinning our tox version. Given that we're preparing to release 0.23.0 pinning is the fastest solution in the short term, we can adjust things after the release is out.
mtreinish
added
type: qa
|
Thank you for opening a new pull request. Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient. While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone. One or more of the the following people are requested to review this:
|
Pull Request Test Coverage Report for Build 4010031749
💛 - Coveralls |
mergify bot
pushed a commit
that referenced
this pull request
Jan 25, 2023
THe most recent release tox, 4.4.0, changed the behavior of how tox interacts with constraints files. It is raising an error because it doesn't like the format of our constraints file in qiskit. This commit works around this by pinning our tox version. Given that we're preparing to release 0.23.0 pinning is the fastest solution in the short term, we can adjust things after the release is out. (cherry picked from commit 85800ca)
mergify bot
added a commit
that referenced
this pull request
Jan 25, 2023
THe most recent release tox, 4.4.0, changed the behavior of how tox interacts with constraints files. It is raising an error because it doesn't like the format of our constraints file in qiskit. This commit works around this by pinning our tox version. Given that we're preparing to release 0.23.0 pinning is the fastest solution in the short term, we can adjust things after the release is out. (cherry picked from commit 85800ca) Co-authored-by: Matthew Treinish <mtreinish@kortar.org>
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.
Summary
The most recent release tox, 4.4.0, changed the behavior of how tox interacts with constraints files. It is raising an error because it doesn't like the format of our constraints file in qiskit. This commit works around this by pinning our tox version. Given that we're preparing to release 0.23.0 pinning is the fastest solution in the short term, we can adjust things after the release is out.
Details and comments