- 18 Mar, 2015 6 commits
-
-
jette authored
-
jette authored
Logic was bad in last commit
-
jette authored
-
jette authored
Fix bug that can permit someone to kill job array belonging to another user.
-
jette authored
If a job is submitted with the option --mem=0, then once the job is allocated resources, reset that value to the amount of memory on the allocated node with the smallest amount of memory. This is probably the best option for right now. The downside is that if the job is requeued, its memory size will no longer be the total memory on all nodes if the cluster is heterogeneous. On the upside, some memory data is available for accounting purposes. bug 1526
-
jette authored
Fix support for --mem=0 (all memory of a node) with select/cons_res plugin. Previously the job would not have it's memory constrained, but it would not make that memory unavailable to other jobs either. bug 1526
-
- 17 Mar, 2015 3 commits
-
-
jette authored
Conflicts: src/sbatch/opt.c
-
Aaron Knister authored
This was previously added to v14.11
-
David Bigagli authored
export "all" if -V given to qsub wrapper
-
- 16 Mar, 2015 3 commits
-
-
Aaron Knister authored
-
jette authored
-
jette authored
Added new SchedulerParameters value of bf_min_age_reserve. The backfill scheduler will not reserve resources for pending jobs until they have been pending for at least the specified number of seconds. This can be valuable if jobs lack time limits or all time limits have the same value.
-
- 14 Mar, 2015 1 commit
-
-
Morris Jette authored
-
- 13 Mar, 2015 7 commits
-
-
Morris Jette authored
-
Morris Jette authored
Increase maximum MaxArraySize configuration parameter value from 1,000,001 to 4,000,001. bug 1535
-
David Bigagli authored
-
Josh Samuelson authored
-
Nathan Yee authored
Also fix a tests so that multiple nodes are not required.
-
Morris Jette authored
-
Morris Jette authored
-
- 12 Mar, 2015 7 commits
-
-
Morris Jette authored
The data could be purged after job completion
-
Marlys Kohnke authored
-
Morris Jette authored
The json m4 script has a bad variable name.
-
Morris Jette authored
The power consumption threasholds are percentages, so they needed to be divided by 100 for proper use.
-
Morris Jette authored
Intervals below 10 seconds on a Cray system will occasionally result in making scheduling decisions based upon old power consumption data. May even require larger values for larger systems.
-
Morris Jette authored
-
Morris Jette authored
Added LaunchParameters configuration parameter. Have srun command test locally for the executable file if LaunchParameters=test_exec or the environment variable SLURM_TEST_EXEC is set. Without this an invalid command will generate one error message per task launched.
-
- 11 Mar, 2015 13 commits
-
-
Morris Jette authored
Cray - Fix for launching batch step within an existing job allocation. bug 1509
-
Morris Jette authored
Change check of batch step ID from NO_VAL to SLURM_BATCH_SCRIPT for better consistency.
-
Morris Jette authored
-
Morris Jette authored
-
David Bigagli authored
-
Morris Jette authored
Conflicts: src/slurmd/slurmstepd/task.c src/squeue/print.c
-
Morris Jette authored
This should not be a problem in v14.03, but the logic will be important in v14.11 due to larger job arrays being supported.
-
Morris Jette authored
-
Morris Jette authored
Make sure variables are initialized before passing a pointer to them as a function argument. The variable is set in the underlying function, so this is mostly cosmetic.
-
Morris Jette authored
Partially revert commit 8d91ae22 The bug was introduced in version 14.11.0-pre4. bug 1504
-
Brian Christiansen authored
-
Nathan Yee authored
Also replaces some spaces with tabs. bug 1354
-
Morris Jette authored
-