- 02 Mar, 2017 15 commits
-
-
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
-
Morris Jette authored
-
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
-
Doug Jacobsen authored
Bug 3523.
-
Tim Wickberg authored
NO_VAL is no longer set; it's NO_VAL64 now on memory values.
-
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
Update commit e58c2282 in order to take advantage of new functions and variables available in version 17.02. bug 3516
-
Morris Jette authored
-
Morris Jette authored
bug 3516
-
Morris Jette authored
-
Morris Jette authored
from 10 to 100. bug 3516
-
Morris Jette authored
-
- 01 Mar, 2017 9 commits
-
-
Danny Auble authored
# Conflicts: # src/slurmctld/job_mgr.c
-
Alejandro Sanchez authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
- 28 Feb, 2017 7 commits
-
-
Danny Auble authored
-
Danny Auble authored
Looks like there were other places not locked. Bug 3515
-
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
-
Gennaro Oliva authored
-
- 27 Feb, 2017 9 commits
-
-
Tim Wickberg authored
Has never been documented, and has never done anything. Bug 3379.
-
Gennaro Oliva authored
Bug 3507.
-
Morris Jette authored
bug 3140
-
Morris Jette authored
This can be used to print a the core's assocatied with a specific node based upon an offset and lenght within a global core_bitmap
-
Morris Jette authored
scontrol modified to report core IDs for reservation containing individual cores. bug 3140
-
Morris Jette authored
-
Daniel Letai authored
-
Morris Jette authored
-
Morris Jette authored
-