- 05 May, 2014 6 commits
-
-
Morris Jette authored
Avoid build Lua script build error with --enable-developer. There was an unused variable, so it never reporting a valid LUA when built with that option.
-
Morris Jette authored
-
Morris Jette authored
In version 14.03.2 was using "slurm_<jobid>_4294967294.out" due to error in job array logic.
-
Morris Jette authored
No change in logic, only clean up function description.
-
Morris Jette authored
-
Morris Jette authored
Enforcement of file allocations requires use of task/cgroup.
-
- 02 May, 2014 10 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
cbcea672
-
Danny Auble authored
situations where the association tree has multiple grp limits, only honor the first one.
-
Danny Auble authored
-
Danny Auble authored
This is for bug 775
-
Danny Auble authored
-
Danny Auble authored
Conflicts: src/slurmd/slurmstepd/slurmstepd_job.c
-
Danny Auble authored
-
Danny Auble authored
-
- 01 May, 2014 4 commits
-
-
Danny Auble authored
regression from 2a674aee
-
Danny Auble authored
-
Danny Auble authored
is running.
-
Danny Auble authored
-
- 30 Apr, 2014 7 commits
-
-
Morris Jette authored
-
David Bigagli authored
together.
-
Morris Jette authored
-
Morris Jette authored
Switch/nrt - Properly track usage of CAU and RDMA resources with multiple tasks per compute node. Previous logic would allocate resources once per task and then deallocate once per node, leaking CMA and RDMA resources and preventing their use by future jobs.
-
Morris Jette authored
If a job is held, then only release it with the "scontrol release <jobid>" command rather than a simple reset of the job's priority. This is needed to support job arrays better. Otherwise a priority reset of a job array would free all requeued/held jobs from that job array rather than leaving them held.
-
Morris Jette authored
-
Morris Jette authored
If a job's priority is set non-zero then always clear the JOB_SPECIAL_EXIT job state flag, not only when the prior state is HELD_USER or HELD. I'm not sure how the job could have cleared the HELD state and changed to NO_REASON, but this would fix the problem. bug 760
-
- 29 Apr, 2014 2 commits
-
-
Morris Jette authored
Change the integer to hex function to support 32-bit unsigned integers and exit on systems with more than 32 cpus per node since Expect can not work with numbers so large.
-
David Bigagli authored
-
- 28 Apr, 2014 10 commits
-
-
Morris Jette authored
This corrects some anomalies in task_id handling. The most significant fallout is the "%a" task ID printed for a NOT array job is now 0xfffffffe rather than 0xfffe, but this should not be used anyway.
-
Morris Jette authored
If the job's stdout or stderr file name contain a "%A" (Job array ID) and it is not a job array, then treat like "%j" (job ID).
-
Morris Jette authored
This actually causes more problems since there are a bunch of places where we set the reason only if it was previously NO_REASON, but we want to treat this the same way, i.e. untested. Adding logic everywhere to clear and reset this value seem to create too much overhead for very little value.
-
Morris Jette authored
There were a couple of cases where a job's reason should have been set, but was not. In addition the state_desc string should have been cleared in some cases, but was not.
-
Morris Jette authored
Plus clear a job's state_desc when the reason is set to NO_REASON
-
Danny Auble authored
-
Danny Auble authored
in 2.0 :)
-
Morris Jette authored
See bug 757
-
Morris Jette authored
Previously partition priority was only considered when used as a component of a job's priority with the priority/multifactor plugin. Now the partition priority is considered first, as documented, and the job priority is considered second. bug 764
-
Morris Jette authored
-
- 26 Apr, 2014 1 commit
-
-
Stuart Midgley authored
Add --priority option to the salloc, sbatch and srun commands.
-