Skip to content

Ensure k8s pod names/labels are RFC 1123 compliant #4171

Ensure k8s pod names/labels are RFC 1123 compliant

Ensure k8s pod names/labels are RFC 1123 compliant #4171

Triggered via pull request October 18, 2024 13:33
Status Failure
Total duration 25m 58s
Artifacts 4

ci.yaml

on: pull_request
Matrix: main-test-suite
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 warning
main-test-suite (3.9)
Process completed with exit code 2.
main-test-suite (3.11)
The job was canceled because "_3_9" failed.
main-test-suite (3.11)
The operation was canceled.
main-test-suite (3.10)
The job was canceled because "_3_9" failed.
main-test-suite (3.10)
The operation was canceled.
main-test-suite (3.12)
The job was canceled because "_3_9" failed.
main-test-suite (3.12)
The operation was canceled.
main-test-suite (3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
runinfo-3.10-3639-merge-57e5446213051b8a0923d205152865b8247b2380
62.1 MB
runinfo-3.11-3639-merge-57e5446213051b8a0923d205152865b8247b2380
39.2 MB
runinfo-3.12-3639-merge-57e5446213051b8a0923d205152865b8247b2380
67.9 MB
runinfo-3.9-3639-merge-57e5446213051b8a0923d205152865b8247b2380
60.1 MB