- 28 Jun, 2013 23 commits
-
-
Morris Jette authored
-
Stephen Trofinoff authored
A simple one-line fix to the "_adjust_cpus_nppcu" function that I had added. I had added this function as part of the NPPCU functionality; however it wasn't a problem until that squeue patch. That was because then squeue had been updated to use this function and in this one case the default value for the internal variable "ntasks_per_core" wound up not being the 0xffff (65535) that I previously had coded for (as in "select/cons_res") but instead was 0. Therefore, in that adjustment function of mine, I simply added a second clause to the if-statment where I check for the sentinel value that also checks whether it is 0. This resolved the problem. Because we do not usually use "select/serial", I did not notice this.
-
Danny Auble authored
-
Morris Jette authored
-
Morris Jette authored
-
Phil Eckert authored
-
Morris Jette authored
-
Daniel M. Weeks authored
-
Morris Jette authored
This can happen if something outside of Slurm opens the srun socket and writes to it, since the data will not be of a form that Slurm can decode. Bug 354
-
Morris Jette authored
Rather than a job
-
Morris Jette authored
This removes logic added three years ago that would automatically set a job's cpus_per_task value in order to reset a job's mem_per_cpu value and scale the cpus_per_task by the same value. Equivalent logic did not exist in the step allocation logic. Just return an error instead. This change will be made in Slurm version 2.6, but this batch is made for version 2.5. The original patch introducing the problem is in commit: cc00cc70bug 352
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Nathan Yee authored
-
Danny Auble authored
enum.
-
Morris Jette authored
-
- 27 Jun, 2013 12 commits
-
-
Morris Jette authored
This removes logic added three years ago that would automatically set a job's cpus_per_task value in order to reset a job's mem_per_cpu value and scale the cpus_per_task by the same value. Equivalent logic did not exist in the step allocation logic. Just return an error instead. This change will be made in Slurm version 2.6, but this batch is made for version 2.5. The original patch introducing the problem is in commit: cc00cc70bug 352
-
Rod Schultz authored
Bug 351
-
Morris Jette authored
-
Morris Jette authored
-
Matthieu Hautreux authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
This is extends the logic of commit ba58d59c to the following RPC types: job complete batch script complete and job step complete
-
Morris Jette authored
-
Morris Jette authored
Related to bug 326
-
Danny Auble authored
-
- 26 Jun, 2013 5 commits
-
-
Morris Jette authored
-
Morris Jette authored
We've seen expect not pick up the full user name in some cases, but truncate it.
-
Morris Jette authored
-
Morris Jette authored
Note, we are switching to the ubuntu version numbering scheme: last two digits of the year for the major version number month number for the minor version number 13.12 == 2013 December
-
Martin Perry authored
In acct_gather_energy/rapl initialization, if the fopen of /proc/cpuinfo fails we should treat this as a fatal condition rather than continue. Patch is attached. Problem found by Coverity tool, CID 20186 bug 331
-