Nathan Vance <naterva...@gmail.com> writes: > Here's what I get when I run it in various ways (positional argument job.sh > bolded): > # sbatch *job.sh* > sbatch: error: time_limit: 4294967294 > sbatch: error: Batch job submission failed: Unspecified error > # sbatch --time=0-07:00:00 *job.sh* > sbatch: error: time_limit: 420 > sbatch: error: Batch job submission failed: Unspecified error > # sbatch *job.sh* --time=0-07:00:00 > sbatch: error: time_limit: 4294967294 > sbatch: error: Batch job submission failed: Unspecified error > > 4294967294 = 2^32 - 2 is the default time limit, which means that on my > third run of this script, the time argument is completely ignored! This is > bad, especially for people who are used to the command line where almost > every program uses an argument parsing library like getopt that works in a > manner that's predictable, both for the programmer and for the user.
It is by design, because people often need to give arguments or options to their jobscript, e.g., sbatch --time=1-0:0:0 myjob.sh inputfile -- Regards, Bjørn-Helge Mevik, dr. scient, Department for Research Computing, University of Oslo
signature.asc
Description: PGP signature
