Conversation
Add more tox environments, expanding the test coverage as follows: * Ansible Core versions 2.18–2.20 (these are the versions currently supported upstream), and 2.16 (this is the version packaged in the latest Ubuntu LTS) * OpenStack clients matching OpenStack Epoxy and Flamingo (these are the two most recent OpenStack releases), and Caracal (packaged in the latest Ubuntu LTS). As of tox 4.47.1, if a testenv factor is a bare version number, and that version number starts with 2 or 3, tox looks for a Python interpreter matching that version. Thus, if a testenv name includes the string "ansible-2.19", it looks for a Python interpreter for the 2.19 version (which never existed). This is intentional behaviour in tox, and will not be fixed. Therefore, name the testenvs "ansible2.19" (etc.), without the hyphen. References: https://docs.ansible.com/projects/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix https://packages.ubuntu.com/noble/ansible-core https://releases.openstack.org/ https://packages.ubuntu.com/noble/python3-openstackclient https://packages.ubuntu.com/noble/python3-heatclient https://packages.ubuntu.com/noble/python3-openstacksdk tox-dev/tox#3850 (comment)
Add coverage for multiple ansible-core versions.
* Add the same matrix for Ansible Core releases as in the GitLab pipeline * Split "build" and "test" jobs as in the GitLab pipeline
colder-is-better
approved these changes
Mar 5, 2026
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.
Add more tox environments, expanding the test coverage as follows:
Ansible Core versions 2.18–2.20 (these are the versions currently
supported upstream), and 2.16 (this is the version packaged in the
latest Ubuntu LTS)
OpenStack clients matching OpenStack Epoxy and Flamingo (these are
the two most recent OpenStack releases), and Caracal (packaged in
the latest Ubuntu LTS).
As of tox 4.47.1, if a testenv factor is a bare version number, and
that version number starts with 2 or 3, tox looks for a Python
interpreter matching that version. Thus, if a testenv name includes
the string "ansible-2.19", it looks for a Python interpreter for the
2.19 version (which never existed).
This is intentional behaviour in tox, and will not be fixed.
Therefore, name the testenvs "ansible2.19" (etc.), without the hyphen.
References:
https://docs.ansible.com/projects/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-core-support-matrix
https://packages.ubuntu.com/noble/ansible-core
https://releases.openstack.org/
https://packages.ubuntu.com/noble/python3-openstackclient
https://packages.ubuntu.com/noble/python3-heatclient
https://packages.ubuntu.com/noble/python3-openstacksdk
tox-dev/tox#3850 (comment)