[Breaking Change] Make Mesh-Level Boundary Conditions Usable without "User" flag (now without bitrot) #1168
Triggered via pull request
September 28, 2024 16:56
Status
Failure
Total duration
26m 26s
Artifacts
–
ci-extended.yml
on: pull_request
Matrix: perf-and-regression-amdgpu
Matrix: perf-and-regression
Annotations
9 errors and 2 warnings
perf-and-regression-amdgpu (mpi)
Process completed with exit code 1.
|
perf-and-regression-amdgpu (serial)
The job was canceled because "mpi" failed.
|
perf-and-regression-amdgpu (serial)
The operation was canceled.
|
perf-and-regression (cuda, serial)
Process completed with exit code 2.
|
perf-and-regression (host, serial)
The job was canceled because "cuda_serial" failed.
|
perf-and-regression (cuda, mpi)
The job was canceled because "cuda_serial" failed.
|
perf-and-regression (cuda, mpi)
The operation was canceled.
|
perf-and-regression (host, mpi)
The job was canceled because "cuda_serial" failed.
|
perf-and-regression (host, mpi)
The operation was canceled.
|
perf-and-regression-amdgpu (mpi)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
perf-and-regression (cuda, serial)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|