Dropping lower constraints testing
We facing errors related to the new pip resolver, this topic was discussed on the ML and QA team proposed to to test lower-constraints [1]. I propose to drop this test because the complexity and recurring pain needed to maintain that now exceeds the benefits provided by this mechanismes. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html Change-Id: Ide5deeb1313552e76468281971f72b7db11d3801
This commit is contained in:
parent
330ca88aee
commit
95e06997a2
@ -2,7 +2,6 @@
|
|||||||
templates:
|
templates:
|
||||||
- check-requirements
|
- check-requirements
|
||||||
- lib-forward-testing-python3
|
- lib-forward-testing-python3
|
||||||
- openstack-lower-constraints-jobs
|
|
||||||
- openstack-cover-jobs
|
- openstack-cover-jobs
|
||||||
- openstack-python3-wallaby-jobs
|
- openstack-python3-wallaby-jobs
|
||||||
- periodic-stable-jobs
|
- periodic-stable-jobs
|
||||||
|
Loading…
Reference in New Issue
Block a user