Skip to content

Test staging

Test staging #231

Triggered via workflow run June 11, 2024 19:52
@edsiperedsiper
completed 34c9f5e
Status Failure
Total duration 14m 2s
Artifacts

staging-test.yaml

on: workflow_run
Matrix: Container images staging tests / call-test-images-container-architecture
Container images staging tests  /  Cosign verification of container image
5s
Container images staging tests / Cosign verification of container image
Container images staging tests  /  Helm chart test on KIND
1m 57s
Container images staging tests / Helm chart test on KIND
Matrix: Binary packages staging test / call-test-packaging
Matrix: Container images staging tests / call-test-images-container-smoke
run integration tests on GCP  /  Run Terraform set up
2m 4s
run integration tests on GCP / Run Terraform set up
Matrix: run integration tests on GCP / Run integration tests on cloud providers
Matrix: run integration tests on GCP / Run integration tests on KIND
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 8 warnings
Binary packages staging test / amazonlinux2 package tests
Process completed with exit code 1.
Binary packages staging test / amazonlinux2022 package tests
Process completed with exit code 137.
run integration tests on GCP / Run integration tests on KIND (v1.23.5)
Process completed with exit code 1.
run integration tests on GCP / Run integration tests on KIND (v1.22.7)
Process completed with exit code 1.
run integration tests on GCP / Run integration tests on KIND (v1.21.10)
Process completed with exit code 1.
run integration tests on GCP / Run integration tests on cloud providers (gke)
Process completed with exit code 1.
run integration tests on GCP / Run integration tests on KIND (v1.23.5)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mig4/setup-bats@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
run integration tests on GCP / Run integration tests on KIND (v1.23.5)
The following actions uses node12 which is deprecated and will be forced to run on node16: mig4/setup-bats@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run integration tests on GCP / Run integration tests on KIND (v1.22.7)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mig4/setup-bats@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
run integration tests on GCP / Run integration tests on KIND (v1.22.7)
The following actions uses node12 which is deprecated and will be forced to run on node16: mig4/setup-bats@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run integration tests on GCP / Run integration tests on KIND (v1.21.10)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mig4/setup-bats@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
run integration tests on GCP / Run integration tests on KIND (v1.21.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: mig4/setup-bats@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run integration tests on GCP / Run integration tests on cloud providers (gke)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mig4/setup-bats@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
run integration tests on GCP / Run integration tests on cloud providers (gke)
The following actions uses node12 which is deprecated and will be forced to run on node16: mig4/setup-bats@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/