performance-testing #170
performance-testing.yml
on: schedule
performance-testing/docker-build
/
...
/
determine-tag
6s
Matrix: performance-testing/docker-build / docker-build/golden-image (bpr) / build-and-push-docker
Matrix: performance-testing/docker-build / docker-build/golden-image (bpr) / create-manifest
performance-testing/docker-build
/
...
/
determine-tag
4s
performance-testing/docker-build
/
...
/
determine-tag
6s
Matrix: performance-testing/docker-build / docker-build/core-client (bpr) / build-and-push-docker
Matrix: performance-testing/docker-build / docker-build/core-service (bpr) / build-and-push-docker
Matrix: performance-testing/docker-build / docker-build/core-client (bpr) / create-manifest
Matrix: performance-testing/docker-build / docker-build/core-service (bpr) / create-manifest
performance-testing/docker-build
/
...
/
common-nitro-enclave/determine-tag
7s
performance-testing/docker-build
/
...
/
common-nitro-enclave/build-and-push-enclave
2m 8s
performance-testing/docker-build
/
...
/
common-nitro-enclave/sign-image
performance-testing/stop-amd64-runner
35s
Annotations
1 error and 4 warnings
|
performance-testing
Process completed with exit code 1.
|
|
performance-testing/start-amd64-runner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: zama-ai/slab-github-runner@0a812986560d3f10dc65728b1ccb9ae4c48a8a16. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
performance-testing
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, azure/setup-kubectl@776406bce94f63e41d621b960d78ee25c8b76ede, docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
performance-testing
No files were found with the provided path: argo-workflow-logs.txt. No artifacts will be uploaded.
|
|
performance-testing/stop-amd64-runner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: zama-ai/slab-github-runner@0a812986560d3f10dc65728b1ccb9ae4c48a8a16. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
kms-core-logs
|
1.71 KB |
sha256:c831c5333504a658639f7cc570b5e184f40afd1f87a9ec9ddec65ee6db4ad7ba
|
|