Skip to content

fix: only use custom task role name on Fargate when provided (#3469) #378

fix: only use custom task role name on Fargate when provided (#3469)

fix: only use custom task role name on Fargate when provided (#3469) #378

Triggered via push February 6, 2025 13:37
Status Failure
Total duration 16m 16s
Artifacts
Matrix: publish-fargate-worker-image / build_docker_image_amd64
Matrix: publish-fargate-worker-image / build_docker_image_arm64
run-distributed-tests  /  generate-test-matrix
4s
run-distributed-tests / generate-test-matrix
Matrix: run-distributed-tests / run-tests
run-distributed-tests  /  run-tests-windows
6m 12s
run-distributed-tests / run-tests-windows
publish-cloudformation-templates-canary-to-s3  /  put-cloudformation-templates
publish-cloudformation-templates-canary-to-s3 / put-cloudformation-templates
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
run-distributed-tests / run-tests-windows
Process completed with exit code 1.
run-distributed-tests / run-tests (artillery/lambda-bom)
Process completed with exit code 1.
publish-fargate-worker-image / build_docker_image_amd64 (public)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
publish-fargate-worker-image / build_docker_image_amd64 (private)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/