ci: tox-lsr 3.16.0 - fix qemu tox test failures - rename to qemu-ansible-core-X-Y [citest_skip]#117
Merged
ci: tox-lsr 3.16.0 - fix qemu tox test failures - rename to qemu-ansible-core-X-Y [citest_skip]#117
Conversation
…ble-core-X-Y [citest_skip] the latest version of tox 4.49 has a strange issue - it thinks that a tox testenv like `[qemu-ansible-core-2.20]` is specifying python 2.20 which conflicts with the testenv basepython of python 3.latest. There appears to be no way to workaround this. So, rename all of the testenvs to use `major-minor` instead of `major.minor` e.g. `[qemu-ansible-core-2-20]` Signed-off-by: Rich Megginson <rmeggins@redhat.com>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates CI tox/tox-lsr integration to use tox-lsr 3.16.0 and renames qemu/container ansible-core tox environments from dot-separated to dash-separated version identifiers to avoid tox 4.49 misinterpreting them as Python versions. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- The example in
contributing.mdchanges both the separator and the ansible-core version (2.14→2-20); consider only changing the separator (e.g.2.14→2-14) or briefly clarifying why the version itself is being updated to avoid confusion for contributors. - After renaming the matrix
envvalues to usemajor-minor, double-check that all corresponding tox environments (e.g. intox.inior related config) use the same naming convention so that CI and local runs stay aligned.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The example in `contributing.md` changes both the separator and the ansible-core version (`2.14` → `2-20`); consider only changing the separator (e.g. `2.14` → `2-14`) or briefly clarifying why the version itself is being updated to avoid confusion for contributors.
- After renaming the matrix `env` values to use `major-minor`, double-check that all corresponding tox environments (e.g. in `tox.ini` or related config) use the same naming convention so that CI and local runs stay aligned.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
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
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 latest version of tox 4.49 has a strange issue - it thinks that a tox testenv
like
[qemu-ansible-core-2.20]is specifying python 2.20 which conflicts with thetestenv basepython of python 3.latest. There appears to be no way to workaround this.
So, rename all of the testenvs to use
major-minorinstead ofmajor.minore.g.[qemu-ansible-core-2-20]Signed-off-by: Rich Megginson rmeggins@redhat.com
Summary by Sourcery
Update CI tox-lsr version and align qemu/container tox environment names with the new ansible-core naming convention.
CI:
Documentation: