- 23 Apr, 2019 1 commit
-
-
Morris Jette authored
Test was always leaving around a file named "slurm.conf.orig". Now delete the file on test success. bug 6878
-
- 22 Apr, 2019 2 commits
-
-
Danny Auble authored
Bug 6878
-
Ben Roberts authored
Brought the option in line with the "numtasks" option you use when not specifying --step. Preserved backwards compatbility for "numtask" for steps. Also upated docs and expect test. Bug 6861
-
- 21 Apr, 2019 1 commit
-
-
Tim Wickberg authored
-
- 18 Apr, 2019 5 commits
-
-
Dominik Bartkiewicz authored
Properly initialize structures throughout Slurm. Bug 6613
-
Danny Auble authored
Bug 6613
-
Dominik Bartkiewicz authored
Bug 6613
-
Tim Wickberg authored
Regression from aca37654 . Bug 6826. Co-authored-by: Chad Vizino <chad@schedmd.com>
-
Tim Wickberg authored
-
- 17 Apr, 2019 3 commits
-
-
Danny Auble authored
Wrong variable was used. This works fine for 18.08, but in 19.05 this code doesn't work correctly. Bug 6739
-
Ben Roberts authored
Bug 6865
-
Brian Christiansen authored
Bug 6313
-
- 16 Apr, 2019 11 commits
-
-
Nate Rini authored
Bug 6625.
-
Danny Auble authored
-
Danny Auble authored
These are conditions that need to remain constant until something changes on the job to reevaluate. Bug 6625
-
Danny Auble authored
What was happening here is you had to not be >= operator to have the old limits removed. This makes it so it always happens. Bug 6625
-
Brian Christiansen authored
Bug 6625
-
Danny Auble authored
Before we went up the tree to the next assoc_ptr. As we validate an association on the id as well as the uid the assoc_ptr was eventually going to become invalid. Setting it to NULL here solves a bunch of issues with things later on. Bug 6625
-
Danny Auble authored
Bug 6625
-
Nathan Rini authored
Bug 6625.
-
Danny Auble authored
Don't abort when the job doesn't have an association that was removed before the job was able to make it to the database. Bug 6625
-
Brian Christiansen authored
Bug 6625
-
Danny Auble authored
-
- 13 Apr, 2019 4 commits
-
-
Marshall Garey authored
The backfill scheduler keeps a local list of job pointers. Since the backfill scheduler yields locks, it's possible for pending jobs to be canceled and purged in these yield periods. The backfill scheduler then has pointers to now invalid memory, and dereferencing those pointers is undefined behavior and may result in a segfault. This commit prevents purging jobs while the backfill scheduler is running. Bug 6621
-
Danny Auble authored
The next patch will use slurmctld_diag_stats.bf_active to determine if we can purge jobs or not. Bug 6621
-
Danny Auble authored
Bug 6739
-
Paolo Margara authored
Bug 6785.
-
- 12 Apr, 2019 2 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
Update slurm.spec and slurm.spec-legacy as well.
-
- 11 Apr, 2019 1 commit
-
-
Tim Wickberg authored
-
- 10 Apr, 2019 6 commits
-
-
Albert Gil authored
Bug 6608.
-
Dominik Bartkiewicz authored
Bug 6807.
-
Alejandro Sanchez authored
==8640== Thread 5 bckfl: ==8640== Syscall param openat(filename) points to unaddressable byte(s) ==8640== at 0x4A81D0E: open (open64.c:48) ==8640== by 0x5934ABB: _update_job_env (burst_buffer_cray.c:3338) ==8640== by 0x5934ABB: bb_p_job_begin (burst_buffer_cray.c:3962) ... ==8640== Address 0x6b96120 is 16 bytes inside a block of size 61 free'd ==8640== at 0x48369AB: free (vg_replace_malloc.c:530) ==8640== by 0x49D4873: slurm_xfree (xmalloc.c:244) ==8640== by 0x490C317: free_command_argv (run_command.c:249) ==8640== by 0x5934A5C: bb_p_job_begin (burst_buffer_cray.c:3947) ... ==8640== Block was alloc'd at ==8640== at 0x4837B65: calloc (vg_replace_malloc.c:752) ==8640== by 0x49D4566: slurm_xmalloc (xmalloc.c:87) ==8640== by 0x49D4B67: makespace (xstring.c:103) ==8640== by 0x49D4C91: _xstrcat (xstring.c:134) ==8640== by 0x49D4ECF: _xstrfmtcat (xstring.c:280) ==8640== by 0x593497C: bb_p_job_begin (burst_buffer_cray.c:3936) ... Bug 6807.
-
Doug Jacobsen authored
Bug 6807.
-
Doug Jacobsen authored
Bug 6807.
-
Doug Jacobsen authored
Bug 6807.
-
- 05 Apr, 2019 4 commits
-
-
Alejandro Sanchez authored
-
Ben Roberts authored
Updated ControlAddr to point to 127.0.0.1 rather than 123.4.5.6 Bug 6794
-
Ben Roberts authored
Bug 6768.
-
Alejandro Sanchez authored
-