Oops. When adding the MPI testing, I forgot to add the option to allow these jobs to run in the pdebug queue. Because these jobs don't run during the business day, and are pretty quick (once the allocation is granted), that's the preferred queue as pbatch can get bogged down with nightly compute jobs. This is actually why corona is timing out more often than other machines, because I forgot to add it to the core test options as well.
Added pdebug for both MPI testing and normal core testing where it was missing. While I was at it, I reformatted options on some of the other machines to make them in consistent order for readability.
P.S. it's allowed to run CI jobs in pdebug, there's actually an example on the GitLab CI confluence for LC that does just that.
Oops. When adding the MPI testing, I forgot to add the option to allow these jobs to run in the
pdebugqueue. Because these jobs don't run during the business day, and are pretty quick (once the allocation is granted), that's the preferred queue aspbatchcan get bogged down with nightly compute jobs. This is actually why corona is timing out more often than other machines, because I forgot to add it to the core test options as well.Added
pdebugfor both MPI testing and normal core testing where it was missing. While I was at it, I reformatted options on some of the other machines to make them in consistent order for readability.P.S. it's allowed to run CI jobs in
pdebug, there's actually an example on the GitLab CI confluence for LC that does just that.