Skip to content
Dotnet EKS Windows Enablement Canary Testing

Dotnet EKS Windows Enablement Canary Testing #36

Sign in to view logs

Dotnet EKS Windows Enablement Canary Testing

Dotnet EKS Windows Enablement Canary Testing #36

Triggered via schedule November 26, 2024 09:34
@XinRanZhAWSXinRanZhAWS
⁠ 493353a
main
Status Failure
Total duration 6m 26s
Artifacts –

dotnet-windows-canary.yml

on: schedule
Matrix: ec2-windows
Matrix: eks-windows
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
ec2-windows (us-east-1) / dotnet-ec2-windows-attempt-1 / dotnet-ec2-windows
Process completed with exit code 1.
ec2-windows (us-east-1) / dotnet-ec2-windows-attempt-1 / dotnet-ec2-windows
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/
ec2-windows (us-east-1) / publish-metric-attempt-1 / 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/
eks-windows (us-east-1) / dotnet-eks
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/