Open simonbyrne opened 1 year ago
In https://github.com/CliMA/ClimaAtmos.jl/pull/1998#issuecomment-1697818899, we hit an issue where slurm_mem was set globally, and slurm_mem_per_cpu was set as an override. Unfortunately according to the docs, these are mutually exclusive, and so the job would not schedule.
slurm_mem
slurm_mem_per_cpu
At the moment, we just pass the args straight through to sbatch, but we could have some mechanism where we give one priority?
sbatch
Also, should we cancel the whole build if a Slurm submission fails?
In https://github.com/CliMA/ClimaAtmos.jl/pull/1998#issuecomment-1697818899, we hit an issue where
slurm_memwas set globally, andslurm_mem_per_cpuwas set as an override. Unfortunately according to the docs, these are mutually exclusive, and so the job would not schedule.At the moment, we just pass the args straight through to
sbatch, but we could have some mechanism where we give one priority?Also, should we cancel the whole build if a Slurm submission fails?