ci: tox-lsr 3.16.0 - fix qemu tox test failures - rename to qemu-ansible-core-X-Y [citest_skip]#595
Merged
ci: tox-lsr 3.16.0 - fix qemu tox test failures - rename to qemu-ansible-core-X-Y [citest_skip]#595
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 integration to work with tox 4.49 by renaming qemu/container ansible-core tox environments to use dash-separated version identifiers and by bumping tox-lsr to 3.16.0 across GitHub workflows and documentation. 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 contributing.md example was changed from
qemu-ansible-core-2.14toqemu-ansible-core-2-20; if the intent was only to adjust the naming scheme, consider keeping the same ansible-core version (e.g.2-14) to avoid confusing readers about version support changes. - After renaming the tox environments from
x.ytox-yin the workflows, double-check that any corresponding env names in tox.ini and helper scripts are updated consistently so CI and local runs use the same identifiers.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The contributing.md example was changed from `qemu-ansible-core-2.14` to `qemu-ansible-core-2-20`; if the intent was only to adjust the naming scheme, consider keeping the same ansible-core version (e.g. `2-14`) to avoid confusing readers about version support changes.
- After renaming the tox environments from `x.y` to `x-y` in the workflows, double-check that any corresponding env names in tox.ini and helper scripts are updated consistently so CI and local runs use the same identifiers.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 new ansible-core naming scheme.
CI:
Documentation: