Actions
Issue #7739
closedRequirement.yml code doesn't filter by version
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
If you use this requirements.yml file[0], you will end up with 3 collection versions. However, you should only have 1 as the two releases for testing.ansible_testing_content are 4.0.4 and 4.0.6[1] which don't match ">=1.0.0,<=2.0.0", and there's only one release of testing.k8s_demo_collection[2].
To reproduce this in a test environment, change this line[3] to use assertEqual since ANSIBLE_COLLECTION_FIXTURE_COUNT is 1.
[1] https://galaxy-dev.ansible.com/api/v2/collections/testing/ansible_testing_content/versions/
[2] https://galaxy.ansible.com/api/v2/collections/testing/k8s_demo_collection/versions/
Related issues
Actions
Refactors sync to use asyncio more and many tests
The previous sync machinery design was very complicated due to treating the asynchronous coroutines as synchronous code. This rewrites the sync code to have the coroutines track the work instead.
In doing the rewrite several bugs were fixed also:
It also makes many test improvements:
closes #7739 closes #7741 closes #7777