Skip to content

Azure e2e - Run Workflow #330

Azure e2e - Run Workflow

Azure e2e - Run Workflow #330

Triggered via schedule August 27, 2024 16:03
Status Failure
Total duration 17m 0s
Artifacts
params-gen
2s
params-gen
report-workflow  /  report-workflow-relations
5s
report-workflow / report-workflow-relations
create-bee-workflow
8m 9s
create-bee-workflow
create-and-attach-billing-project-to-landing-zone-workflow
2m 4s
create-and-attach-billing-project-to-landing-zone-workflow
run-cromwell-az-e2e  /  run-cromwell-az-e2e
run-cromwell-az-e2e / run-cromwell-az-e2e
delete-billing-project-v2-from-bee-workflow
2m 4s
delete-billing-project-v2-from-bee-workflow
destroy-bee-workflow
4m 3s
destroy-bee-workflow
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
create-and-attach-billing-project-to-landing-zone-workflow
Workflow run has failed
delete-billing-project-v2-from-bee-workflow
Workflow run has failed
create-bee-workflow
The following actions use a deprecated Node.js version and will be forced to run on node20: broadinstitute/workflow-dispatch@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
create-and-attach-billing-project-to-landing-zone-workflow
The following actions use a deprecated Node.js version and will be forced to run on node20: broadinstitute/workflow-dispatch@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
delete-billing-project-v2-from-bee-workflow
The following actions use a deprecated Node.js version and will be forced to run on node20: broadinstitute/workflow-dispatch@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
destroy-bee-workflow
The following actions use a deprecated Node.js version and will be forced to run on node20: broadinstitute/workflow-dispatch@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/