- 12 Jan, 2017 1 commit
-
-
Morris Jette authored
Previous job state information was "PENDING" rather than "REQUEUED" for each job requeued due to a burst buffer error. bug 3388
-
- 11 Jan, 2017 2 commits
-
-
Danny Auble authored
scheduling a Datawarp job. The assoc_mgr lock needs to happen before the bb_state.bb_mutex. One place this could cause deadlock is from src/slurmctld/controller.c _accounting_cluster_ready() which calls clusteracct_storage_g_cluster_tres which inturn calls bb_g_job_set_tres_cnt which calls bb_p_job_set_tres_cnt which will lock the bb_muxtex after the assoc_mgr is already locked. Bug 3389
-
Dominik Bartkiewicz authored
Cache results of bit_set_count() calls. Bug 3393.
-
- 10 Jan, 2017 1 commit
-
-
Morris Jette authored
Accidentally commited to Slurm version 16.05 instead of master
-
- 09 Jan, 2017 7 commits
-
-
Morris Jette authored
3 places where a string pointer referenced an out-of-scope memory location 1 memory leak and 1 unterminated string
-
Morris Jette authored
backfill scheduler: Stop trying to determine expected start time for a job after 2 seconds of wall time. This can happen if there are many running jobs and a pending job can not be started soon. byg 3373
-
Danny Auble authored
mobile devices didn't behave as expected.
-
Danny Auble authored
-
Danny Auble authored
some of the tables (prolog_epilog) were hard to read.
-
Danny Auble authored
-
Dominik Bartkiewicz authored
Bug 3364.
-
- 05 Jan, 2017 1 commit
-
-
Doug Jacobsen authored
Bug 3376.
-
- 04 Jan, 2017 8 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
Fix security issue caused by insecure file path handling triggered by the failure of a Prolog script. To exploit this a user needs to anticipate or cause the Prolog to fail for their job. (This commit is slightly different from the fix to the 15.08 branch.) CVE-2016-10030.
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Tim Wickberg authored
Fix security issue caused by insecure file path handling triggered by the failure of a Prolog script. To exploit this a user needs to anticipate or cause the Prolog to fail for their job. CVE-2016-10030.
-
Morris Jette authored
This modifies the logic in commit e089b63a for better clarity
-
- 03 Jan, 2017 8 commits
-
-
Dominik Bartkiewicz authored
Prevent "stray" jobs from using resources when the srun/salloc will never launch the actual compute tasks. Bug 3344.
-
Dominik Bartkiewicz authored
PluginDir is allowed to be a PATH-style list of directories; remove incorrect test of the variable as if it were a single directory and comment that the check for that is elsewhere. Bug 3361.
-
Tim Wickberg authored
-
Alejandro Sanchez authored
-
Morris Jette authored
Expect is unable to work with more than 32-bit numbers, so it can't properly test task affinity on KNL with 272 threads
-
Tim Wickberg authored
-
Alejandro Sanchez authored
- 2 x Integer handling issues (CONSTANT_EXPRESSION_RESULT)
-
Tim Wickberg authored
Warning flag -Wempty-body in clang-3.7 now errors on this, split macro definition up over multiple lines to silence.
-
- 31 Dec, 2016 1 commit
-
-
Morris Jette authored
Revision to 06fbdd75 Previous logic was causing tests 1.87 and 15.19 to fail sometimes due to a race condition by adding a "Job allocation revoked" message to salloc output even if no allocation occured. bug 3351
-
- 29 Dec, 2016 5 commits
-
-
Roland Fehrenbacher authored
-
Morris Jette authored
Previous logic was failing if no specialized cores configured on node and job wanted to configure some bug 3349
-
Dominik Bartkiewicz authored
Null terminate before strchr().
-
Morris Jette authored
-
Morris Jette authored
This is a new message when "PrologFlags=contain" or "PrologFlags=alloc" is configured. bug 3351
-
- 28 Dec, 2016 3 commits
-
-
Alejandro Sanchez authored
Cancel interactive job if Prolog failure with "PrologFlags=contain" configured. bug 3351
-
Morris Jette authored
Minor fix to commit 1e6b7522 in the case where user specification of specialized cores is disabled. bug 3349
-
Matthieu Hautreux authored
If a job specifies --core-spec and the node has identified specialized cores using the CpuSpecList option which are not the default cores (e.g. the first cores rather than the last cores on each socket), the the user's cores will be selected from those identified in the configuration. bug 3349
-
- 27 Dec, 2016 1 commit
-
-
Morris Jette authored
Was printing int64 using %ld, which generated a warning on some systems
-
- 21 Dec, 2016 1 commit
-
-
Morris Jette authored
Do not allocate specialized cores to jobs using the --exclusive option. bug 3349
-
- 19 Dec, 2016 1 commit
-
-
Morris Jette authored
This commit should be part of b5f621d0 when the man page was removed
-