- 11 Mar, 2017 1 commit
-
-
Danny Auble authored
assoc_mgr_make_tres_str_from_array.
-
- 10 Mar, 2017 5 commits
-
-
Danny Auble authored
-
Tim Shaw authored
array task id. This is combination with the previous commit. Bug 3563
-
Danny Auble authored
-
Danny Auble authored
I also made seff work on a non-standard perl install. I would had loved to do this in multiple commits, but it wasn't that possible.
-
Dominik Bartkiewicz authored
-
- 08 Mar, 2017 10 commits
-
-
Danny Auble authored
moment the dbd is assigning a db_index. Bug 3512 This is a definite culprit of creating runaway jobs.
-
Danny Auble authored
because the dbd is setting a db_index.
-
Danny Auble authored
in the middle of setting db_indexes.
-
Danny Auble authored
multifactor. Almost impossible to make happen, but still a bug.
-
Tim Wickberg authored
The stepd->protocol_version field is not set at this point, if not handled here then the following call to stepd_get_uid will fail as a protocol_version of zero is rejected. This appeared to work in 16.05 and older as the stepd_get_uid() API call used to ignore the invalid protocol_version and return the correct result anyways, but that was fixed in c177ff95. Bug .
-
Tim Shaw authored
correctly with Slurm tools. What this does is replace the incoming string with the gres actually chosen. Continuation of last commit. Bug 3521
-
Danny Auble authored
the database.
-
Thomas Opfer authored
Symbol required for read_slurm_cgroup_conf() call to work. Bug 3550.
-
Morris Jette authored
burst_buffer/cray - Fix parsing for discontinuous allocated nodes. A job allocation of "20,22" must be expressed as "20\n22" when passed to the dw_wlm_cli program. bugs 3540 and 3544
-
Morris Jette authored
-
- 07 Mar, 2017 3 commits
-
-
Morris Jette authored
capmc_resume (Cray resume node script) - Do not disable changing a node's active features if SyscfgPath is configured in the knl.conf file. bug 3533
-
Morris Jette authored
If a job is cancelled by the user while it's allocated nodes are being reconfigured (i.e. the capmc_resume program is rebooting nodes for the job) and the node reconfiguration fails (i.e. the reboot fails), then don't requeue the job but leave it in a cancelled state. Note the JOB_RECONFIG_FAIL state flag is currently only used by capmc_resume, but could be used for other programs responsible for node reboots. bug 3392
-
Morris Jette authored
bug 3538
-
- 03 Mar, 2017 2 commits
-
-
Morris Jette authored
-
Danny Auble authored
-
- 02 Mar, 2017 9 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
This is a partial reversion of commit 69684648 NOTE: sbatch does not support --cpu_bind (although the documentation does list the option) and the --mem_bind options set SBATCH_* environment variables that nothing every looks at. In other words, it needs some work. Bugs 3519 and 3188
-
Felip Moll authored
bug 3525
-
Morris Jette authored
Copy NEWS item updates from v16.05 applied since v17.02.0 tag to to NEWS for v17.02.1
-
Morris Jette authored
Convert a slurmctd power management data structure from array to list in order to eliminate the possibility of zombie child suspend/resume processes. bug 3516
-
Tim Wickberg authored
This now matches the behavior documented in sbatch. This resolves a problem where the maximum cpu frequency would be set to the minimum available on the node by the batch step. This is due to the batch step leaving cpu_freq_{min,max,gov} uninitialized to zero, which is then translated to a request to set the frequency to the lowest available in the node. This did not impact 16.05 or earlier, as a request for a zero frequency was ignored by a quirk of _cpu_freq_freqspec_num. This quirk was removed by commit f40e1c01 before 17.02.0-rc1. Bug 3510.
-
Morris Jette authored
bug 3516
-
Morris Jette authored
from 10 to 100. bug 3516
-
- 01 Mar, 2017 3 commits
-
-
Alejandro Sanchez authored
-
Danny Auble authored
-
Danny Auble authored
-
- 28 Feb, 2017 4 commits
-
-
Dominik Bartkiewicz authored
information about a job to scontrol.
-
Dominik Bartkiewicz authored
-
Danny Auble authored
cause potential deadlock when/if TRES changed in the database and the slurmctld wasn't made aware of the change. This would be very rare. The lock was originally there to keep new jobs from grabbing the assoc information. If the lock was done afterwards the worst case is we get the new information.
-
Danny Auble authored
It was determined we didn't need the write locks on the job and no locks were needed on the node either. Doing these different locked beforehand would create a window where you could get a config write lock
-
- 27 Feb, 2017 3 commits
-
-
Daniel Letai authored
-
Morris Jette authored
This will be triggered after either a burst buffer job_begin function or select plugin job_begin function fails. Without this change, the "squeue -i" and "scontrol show job" commands can report old job state information. bug 3504
-
Tim Wickberg authored
Burst_buffer/cray - Prevent slurmctld daemon abort if "paths" operation fails. Now job will be held. bug 3504
-