Skip to content
Test Suite

make mesh_dir behavior consistent across create_meshing_tasks and create_mesh_manifest_tasks #340

Sign in to view logs

make mesh_dir behavior consistent across create_meshing_tasks and create_mesh_manifest_tasks

make mesh_dir behavior consistent across create_meshing_tasks and create_mesh_manifest_tasks #340

Re-run triggered August 1, 2024 18:53
@william-silversmithwilliam-silversmith
#178
jasonkena:master
Status Failure
Total duration 7m 9s
Artifacts –

test-suite.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
build (3.9)
Process completed with exit code 1.
build (3.11)
The job was canceled because "_3_9" failed.
build (3.11)
Process completed with exit code 1.
build (3.12)
The job was canceled because "_3_9" failed.
build (3.12)
The operation was canceled.
build (3.10)
The job was canceled because "_3_9" failed.
build (3.10)
The operation was canceled.
build (3.8)
The job was canceled because "_3_9" failed.
build (3.8)
The operation was canceled.
build (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/