- 06 Dec, 2011 7 commits
-
-
Morris Jette authored
-
Yuri D'Elia authored
sacct --name follows the same logic as scancel/squeue, limiting the output only to jobs having one of the specified name/s. The job names are simply sent over the wire to be handled by the backend. Both mysql and filetxt backends were updated to handle this new condition. This requires an incompatible protocol change in the job_cond structure. The perl api was also updated.
-
Yuri D'Elia authored
SQUEUE_NAMES was previously introduced for squeue along with --name, but not documented.
-
Morris Jette authored
-
Yuri D'Elia authored
-
Morris Jette authored
The change is due to job's qos and account limits being re-tested more frequently and we want to avoid logging so many messages.
-
Morris Jette authored
Let a job be submitted even if it exceeds a QOS limit. Job will be left in a pending state until the QOS limit or job parameters change. Patch by Phil Eckert, LLNL.
-
- 05 Dec, 2011 6 commits
-
-
Morris Jette authored
-
Morris Jette authored
Patch by Alexander Bersenev (Institute of Mathematics and Mechanics, Russia).
-
Morris Jette authored
-
Morris Jette authored
Conflicts: META NEWS
-
Morris Jette authored
-
Morris Jette authored
-
- 02 Dec, 2011 16 commits
-
-
Danny Auble authored
Conflicts: src/plugins/select/bluegene/bg_job_info.c
-
Danny Auble authored
There was also some bad code that would reset the conn_type of a block to SMALL no matter what type of SMALL it was.
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
Patsh from Rod Schulz, Bull.
-
https://github.com/SchedMD/slurmjette authored
-
jette authored
-
Danny Auble authored
into allowing them.
-
Danny Auble authored
to NULL otherwise.
-
Danny Auble authored
step. If so there is no need to do any step cleanup since the allocation has already been cleaned up.
-
Danny Auble authored
don't need to.
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
looking for 1 midplane, no reason to go through any more than that.
-
Danny Auble authored
when having multiple steps per job.
-
- 01 Dec, 2011 5 commits
-
-
jette authored
MAX should have been MIN
-
jette authored
-
jette authored
-
jette authored
-
jette authored
This was due to a bug in select/cons_res with some configuration optiions and job options, especially if there is more than one thread per core and the job option includes "--threads-per-core=1". Fixes problem reported by CSCS.
-
- 30 Nov, 2011 6 commits
-
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Danny Auble authored
Conflicts: src/slurmctld/job_mgr.c
-
Danny Auble authored
lock was deemed not necessary because the information (db_index) was only internal and was only modified in the same function later which is protected by the write lock.
-
Danny Auble authored
qos on the cluster to fill that in correctly.
-