- 31 Dec, 2014 3 commits
-
-
Morris Jette authored
Expanded --cpu-freq parameters to include min-max:governor specifications. --cpu-freq now supported on salloc and sbatch. Conflicts: NEWS
-
Morris Jette authored
-
Morris Jette authored
-
- 30 Dec, 2014 17 commits
-
-
Morris Jette authored
-
Morris Jette authored
It largely prevents Slurm control over CPU frequency
-
Nathan Yee authored
-
Morris Jette authored
-
Morris Jette authored
This test failed once due to a low CPU frequency. Change the logic to lessen the impact of a low frequency.
-
David Bigagli authored
-
Brian Christiansen authored
Bug 1333
-
Morris Jette authored
No changes in logic
-
David Bigagli authored
-
Danny Auble authored
-
Morris Jette authored
some redundant code from srun was removed
-
Morris Jette authored
Previously it was printing a bunch of garbage
-
Morris Jette authored
It was originally 32-bits so none of the tests for the flag DEBUG_FLAG_CPU_FREQ in step_mgr.c worked at all.
-
Morris Jette authored
The --cpu-freq option from the sbatch/salloc command was NOT logged as part of the RPC NOT being stored in the slurmctld job record NOT return as part of the job information once started (even if the data structure was populated, which was not the case)
-
Morris Jette authored
Previous it just printed the value (e.g. "Low") without any indication of what the information represented.
-
Morris Jette authored
-
Danny Auble authored
Conflicts: NEWS
-
- 29 Dec, 2014 9 commits
-
-
Morris Jette authored
Do so only if the CpuFreq DebugFlag is set
-
Morris Jette authored
The test was assuming the governors configured on a CPU are available to the job, ignoring the configured CpuFreqGovernors value.
-
Danny Auble authored
-
David Bigagli authored
-
Morris Jette authored
Removed mkdir (not the critical bit) then test vestigial errno value so the original cpu environment was never being reset and test1.76 was consistently failing.
-
Morris Jette authored
-
Morris Jette authored
The values are changing between v14.11 and 15.08.
-
Morris Jette authored
The CPU_FREQ values can not be changed unless logic is added to do the translation of values from old format command and save/restore state. Since that logic does not exist, the values were restored to their original values.
-
Morris Jette authored
Make test work if slurm commands or working directory not in search path move test for FastScheduler value into globals
-
- 26 Dec, 2014 1 commit
-
-
Jason Bacon authored
-
- 25 Dec, 2014 1 commit
-
-
Morris Jette authored
-
- 24 Dec, 2014 9 commits
-
-
Morris Jette authored
-
Rod Schultz authored
-
Rod Schultz authored
-
Rod Schultz authored
-
Rod Schultz authored
-
Rod Schultz authored
-
Morris Jette authored
Enable per-partition gang scheduling resource resolution (e.g. the partition can have SelectTypeParameters=CR_CORE, while the global value is CR_SOCKET). bug 1299
-
Morris Jette authored
Added the user name rather than just printing the user ID number. Fixed the format for a job array record ("_" rather than "." separator): Added a GRES field.
-
Nathan Yee authored
-