Skip to content
Application Signals Enablement - DotNet E2E EKS Canary Testing

one region test #21

Sign in to view logs

one region test

one region test #21

Triggered via push August 28, 2024 18:28
@XinRanZhAWSXinRanZhAWS
pushed 5051ee8
dotnetMergeBranch-revert
Status Failure
Total duration 28m 38s
Artifacts –

dotnet-eks-e2e-canary-test.yml

on: push
Matrix: dotnet-e2e-eks-test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
dotnet-e2e-eks-test (ap-northeast-2) / dotnet-e2e-eks-test
Process completed with exit code 1.
dotnet-e2e-eks-test (ap-northeast-2) / dotnet-e2e-eks-test
Process completed with exit code 1.
dotnet-e2e-eks-test (ap-northeast-2) / dotnet-e2e-eks-test
Process completed with exit code 1.
dotnet-e2e-eks-test (ap-northeast-2) / dotnet-e2e-eks-test
Process completed with exit code 1.
dotnet-e2e-eks-test (ap-northeast-2) / dotnet-e2e-eks-test
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/aws-secretsmanager-get-secrets@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
dotnet-e2e-eks-test (ap-northeast-2) / emit-metric / publish-result
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/aws-secretsmanager-get-secrets@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/