Skip to content

Bind v1 and v3 namespaces if created and use v3 for provider #4965

Bind v1 and v3 namespaces if created and use v3 for provider

Bind v1 and v3 namespaces if created and use v3 for provider #4965

Triggered via pull request September 11, 2023 19:58
Status Cancelled
Total duration 8m 5s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
check_commit
6s
check_commit
lint_po
4s
lint_po
Matrix: test
update_manifest
0s
update_manifest
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
test (pulp)
Canceling since a higher priority waiting request for '1881/merge-Galaxy CI' exists
test (pulp)
The operation was canceled.
test (azure)
Canceling since a higher priority waiting request for '1881/merge-Galaxy CI' exists
test (azure)
The operation was canceled.
test (s3)
Canceling since a higher priority waiting request for '1881/merge-Galaxy CI' exists
test (s3)
The operation was canceled.
lint_po
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
check_commit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/