-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Force PyYAML version that can be installed #1917
CI: Force PyYAML version that can be installed #1917
Conversation
Build failed. ❌ ansible-galaxy-importer FAILURE in 5m 19s (non-voting) |
recheck |
Build succeeded. ❌ ansible-galaxy-importer FAILURE in 4m 59s (non-voting) |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 27s (non-voting) |
CI: Force PyYAML version that can be installed SUMMARY Sibling to ansible-collections/community.aws#1917. ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Mike Graves <mgraves@redhat.com>
CI: Force PyYAML version that can be installed SUMMARY Sibling to ansible-collections/community.aws#1917. ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Mike Graves <mgraves@redhat.com> (cherry picked from commit 7dfdeb3)
CI: Force PyYAML version that can be installed SUMMARY Sibling to ansible-collections/community.aws#1917. ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Mike Graves <mgraves@redhat.com> (cherry picked from commit 7dfdeb3)
CI: Force PyYAML version that can be installed SUMMARY Sibling to ansible-collections/community.aws#1917. ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Mike Graves <mgraves@redhat.com> (cherry picked from commit 7dfdeb3)
[PR #1707/7dfdeb3d backport][stable-6] CI: Force PyYAML version that can be installed This is a backport of PR #1707 as merged into main (7dfdeb3). SUMMARY Sibling to ansible-collections/community.aws#1917. ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Mike Graves <mgraves@redhat.com>
Build succeeded (gate pipeline). ❌ ansible-galaxy-importer FAILURE in 5m 21s (non-voting) |
002b139
into
ansible-collections:main
Backport to stable-5: 💔 cherry-picking failed — conflicts found❌ Failed to cleanly apply 002b139 on top of patchback/backports/stable-5/002b139a2fedc630bd46eadea7e5e2b077a9bb0a/pr-1917 Backporting merged PR #1917 into main
🤖 @patchback |
Backport to stable-6: 💚 backport PR created✅ Backport PR branch: Backported as #1918 🤖 @patchback |
CI: Force PyYAML version that can be installed SUMMARY Currently integration tests with ansible/ansible-zuul-jobs#1816 still fail when installing some requirements: 2023-08-22 05:53:46.350742 | TASK [ansible-test : Install python requirements] [...] 2023-08-22 05:53:53.860850 | controller | Collecting PyYAML<5.5,>=3.10 (from awscli->-r /home/zuul-worker/.ansible/collections/ansible_collections/community/aws/test-requirements.txt (line 19)) 2023-08-22 05:53:53.866271 | controller | Downloading PyYAML-5.4.1.tar.gz (175 kB) 2023-08-22 05:53:53.878160 | controller | �������������������������������������� 175.1/175.1 kB 19.0 MB/s eta 0:00:00 2023-08-22 05:53:54.065094 | controller | Installing build dependencies: started 2023-08-22 05:53:58.372457 | controller | Installing build dependencies: finished with status 'done' 2023-08-22 05:53:58.373282 | controller | Getting requirements to build wheel: started 2023-08-22 05:53:58.680407 | controller | Getting requirements to build wheel: finished with status 'error' 2023-08-22 05:53:58.689654 | controller | error: subprocess-exited-with-error (https://b3e35e76f7fc3e0cf6b5-d430d94f79a1de67219002b64dcf7484.ssl.cf1.rackcdn.com/1904/63f02a9c37ef75f9dcf25159fb4033d6edf146ee/check/integration-community.aws-1/b2f8016/job-output.txt) Tries to work around this problem by pinning the PyYAML version to 5.3.1 (see also yaml/pyyaml#736). ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Alina Buzachis Reviewed-by: Mark Chappell Reviewed-by: Felix Fontein <felix@fontein.de> Reviewed-by: Markus Bergholz <git@osuv.de> (cherry picked from commit 002b139)
@alinabuzachis @tremble @markuman thanks a lot for reviewing and your comments! |
CI: Force PyYAML version that can be installed SUMMARY Currently integration tests with ansible/ansible-zuul-jobs#1816 still fail when installing some requirements: 2023-08-22 05:53:46.350742 | TASK [ansible-test : Install python requirements] [...] 2023-08-22 05:53:53.860850 | controller | Collecting PyYAML<5.5,>=3.10 (from awscli->-r /home/zuul-worker/.ansible/collections/ansible_collections/community/aws/test-requirements.txt (line 19)) 2023-08-22 05:53:53.866271 | controller | Downloading PyYAML-5.4.1.tar.gz (175 kB) 2023-08-22 05:53:53.878160 | controller | �������������������������������������� 175.1/175.1 kB 19.0 MB/s eta 0:00:00 2023-08-22 05:53:54.065094 | controller | Installing build dependencies: started 2023-08-22 05:53:58.372457 | controller | Installing build dependencies: finished with status 'done' 2023-08-22 05:53:58.373282 | controller | Getting requirements to build wheel: started 2023-08-22 05:53:58.680407 | controller | Getting requirements to build wheel: finished with status 'error' 2023-08-22 05:53:58.689654 | controller | error: subprocess-exited-with-error (https://b3e35e76f7fc3e0cf6b5-d430d94f79a1de67219002b64dcf7484.ssl.cf1.rackcdn.com/1904/63f02a9c37ef75f9dcf25159fb4033d6edf146ee/check/integration-community.aws-1/b2f8016/job-output.txt) Tries to work around this problem by pinning the PyYAML version to 5.3.1 (see also yaml/pyyaml#736). ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Alina Buzachis Reviewed-by: Mark Chappell Reviewed-by: Felix Fontein <felix@fontein.de> Reviewed-by: Markus Bergholz <git@osuv.de>
I created a manual backport to stable-5 in #1919. |
[stable-5] Force PyYAML version that can be installed. (#1917)
…/stable-6/002b139a2fedc630bd46eadea7e5e2b077a9bb0a/pr-1917 [PR #1917/002b139a backport][stable-6] CI: Force PyYAML version that can be installed
[manual backport stable-5] Force PyYAML version that can be installed. (#1707) CI: Force PyYAML version that can be installed SUMMARY Sibling to ansible-collections/community.aws#1917. ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Mike Graves mgraves@redhat.com (cherry picked from commit 7dfdeb3) SUMMARY ISSUE TYPE Bugfix Pull Request Docs Pull Request Feature Pull Request New Module Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: GomathiselviS Reviewed-by: Helen Bailey <hebailey@redhat.com>
CI: Force PyYAML version that can be installed SUMMARY Sibling to ansible-collections/community.aws#1917. ISSUE TYPE Test Pull Request COMPONENT NAME integration tests Reviewed-by: Mike Graves <mgraves@redhat.com>
SUMMARY
Currently integration tests with ansible/ansible-zuul-jobs#1816 still fail when installing some requirements:
(https://b3e35e76f7fc3e0cf6b5-d430d94f79a1de67219002b64dcf7484.ssl.cf1.rackcdn.com/1904/63f02a9c37ef75f9dcf25159fb4033d6edf146ee/check/integration-community.aws-1/b2f8016/job-output.txt)
Tries to work around this problem by pinning the PyYAML version to 5.3.1 (see also yaml/pyyaml#736).
ISSUE TYPE
COMPONENT NAME
integration tests