tox 4 impact to charm testing
Bug #2002788 reported by
James Page
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Test Infra |
Invalid
|
Undecided
|
Unassigned | ||
Antelope |
In Progress
|
Critical
|
Unassigned | ||
Ussuri |
In Progress
|
Critical
|
Unassigned | ||
Victoria |
In Progress
|
Critical
|
Unassigned | ||
Wallaby |
In Progress
|
Critical
|
Unassigned | ||
Xena |
In Progress
|
Critical
|
Unassigned | ||
Yoga |
In Progress
|
Critical
|
Unassigned | ||
Zed |
In Progress
|
Critical
|
Unassigned |
Bug Description
The recent release of tox 4 introduces a number of breaking changes which impact the testing within the OpenStack Charms.
The strategy for resolution is as follows:
master branch will move forward and use tox >= 4 with the required changes being made across the charm set.
stable/* branches will pin tox < 4 to minimise code churn within existing released stable charms.
This bug will be used for high level tracking of changes to resolve this and unblock OpenStack Charms CI.
Changed in charm-test-infra: | |
status: | In Progress → Invalid |
importance: | Critical → Undecided |
To post a comment you must log in.
Reviews for stable branches where tox will be pinned < 4:
https:/ /review. opendev. org/q/topic: pin-tox