Open sbryngelson opened 2 days ago
CI Batch jobs that don't get nodes (due to queue wait times or down nodes or whatever) don't trigger a failure stop code. For example,
Run bash .github/workflows/frontier/submit.sh .github/workflows/frontier/test.sh Submitted batch job 2070639 Error: The operation was canceled.
and
Run cat test-gpu.out cat: test-gpu.out: No such file or directory Error: Process completed with exit code
from https://github.com/MFlowCode/MFC/actions/runs/9748333690/job/26903120742
I'm sure there is a bash or slurm command that would trigger a proper stop error code.
CI Batch jobs that don't get nodes (due to queue wait times or down nodes or whatever) don't trigger a failure stop code. For example,
and
from https://github.com/MFlowCode/MFC/actions/runs/9748333690/job/26903120742
I'm sure there is a bash or slurm command that would trigger a proper stop error code.