Port-forward: Completion for exposed ports on services #686
Triggered via pull request
September 22, 2024 23:01
Status
Failure
Total duration
6h 0m 26s
Artifacts
–
Annotations
9 errors and 2 warnings
build-and-test (snapshot, true)
Process completed with exit code 2.
|
build-and-test (29.3, v1.26.1)
The job running on runner GitHub Actions 18 has exceeded the maximum execution time of 360 minutes.
|
build-and-test (29.3, v1.26.1)
The operation was canceled.
|
build-and-test (29.3, v1.25.6)
The job running on runner GitHub Actions 20 has exceeded the maximum execution time of 360 minutes.
|
build-and-test (29.3, v1.25.6)
The operation was canceled.
|
build-and-test (29.3, v1.24.10)
The job running on runner GitHub Actions 7 has exceeded the maximum execution time of 360 minutes.
|
build-and-test (29.3, v1.24.10)
The operation was canceled.
|
build-and-test (29.3, v1.23.12)
The job running on runner GitHub Actions 15 has exceeded the maximum execution time of 360 minutes.
|
build-and-test (29.3, v1.23.12)
The operation was canceled.
|
build-and-test (snapshot, true)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
build-and-test (snapshot, true)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2, actions/checkout@v3, helm/[email protected], nick-fields/retry@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|