- 26 Apr, 2019 4 commits
-
-
Nate Rini authored
No functional change. Bug 6832.
-
Nate Rini authored
Otherwise, we could send communication packets bigger than max_allowed_packet. Bug 6832. Co-authored-by:
Tim Wickberg <tim@schedmd.com>
-
Alejandro Sanchez authored
Regression introduced in 8d643e79. Bug 6832.
-
- 24 Apr, 2019 4 commits
-
-
Moe Jette authored
when not the head job. Bug 6837 For more in depth explanation see comment 24
-
Albert Gil authored
Bug 6873
-
Albert Gil authored
When specifying -j and not -s then non-eligible jobs will be shown by sacct. Time windows can also be used with -S and -E. If --state is also used then non-eligible jobs won't be shown, because non-eligible are not actually PD. Bug 6873 # Conflicts: # NEWS
-
Ben Roberts authored
Bug 6805
-
- 23 Apr, 2019 5 commits
-
-
Danny Auble authored
Bug 6898
-
Danny Auble authored
Continuation of commit cc153e03
-
Albert Gil authored
Cancelled jobs before start have time_start=0 in the DB, but their time_end!=0 (the cancel time). Query fixed to handle properly these cases for -s PD. Bug 6894
-
Danny Auble authored
Bug 6878
-
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 1 commit
-
-
Tim Wickberg authored
-