- 13 Mar, 2015 3 commits
-
-
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 15 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
-
Morris Jette authored
Add new configuration parameter "set_watts" to explicitly set every node's power cap to the same value. Improve accuracy of power cap data logging. Fix logic for changing configuration values with SIGHUP or "scontrol reconfig" command. Correct power distribution calculation.
-
Brian Christiansen authored
Restores same behavior prior to ce32018a. Bug 1513
-
- 10 Mar, 2015 5 commits
-
-
Morris Jette authored
A fairly major update to use JSON data strurctures directly to set power caps for better scalability and performance. Added logic to send STDIN to the capmc command (with the JSON data).
-
Danny Auble authored
This is for bug 1514
-
Morris Jette authored
Relocate where power plugin is told about new job allocation. Previous logic failed to work for job allocated resources at submission time (top priority job does not need to go through the same job scheduling logic as jobs that are already in the queue, and thus failed to notify the power plugin at start time).
-
Brian Christiansen authored
-
Morris Jette authored
-
- 09 Mar, 2015 3 commits
-
-
Danny Auble authored
before.
-
David Bigagli authored
-
David Bigagli authored
-
- 06 Mar, 2015 2 commits
-
-
Brian Christiansen authored
Bug 1507
-
Morris Jette authored
-
- 05 Mar, 2015 5 commits
-
-
Danny Auble authored
-
Danny Auble authored
fails addition to commit 2c83bf4e
-
Danny Auble authored
message comes in
-
David Bigagli authored
-
David Bigagli authored
-