- 02 May, 2019 3 commits
-
-
Broderick Gardner authored
Bug 6064
-
Broderick Gardner authored
On requeue, the origin cluster job record is copied to submit to sibling clusters. If the job was originally submitted to accept cluster default account, partition, etc, those fields are now filled in on the origin. Here we add flags to indicate that those fields need to be cleared on resubmission to siblings. Bug 6064
-
Broderick Gardner authored
This is a holdover from when the fed job_info list was added. The cluster lock has to be cleared from both the job_ptr and the job_info. Bug 6064
-
- 30 Apr, 2019 1 commit
-
-
Danny Auble authored
Blessed by Tim.
-
- 29 Apr, 2019 10 commits
-
-
Brian Christiansen authored
when one offset passes and other fails. Bug 6892
-
Nate Rini authored
Bug 6513.
-
Brian Christiansen authored
Bug 6513
-
Brian Christiansen authored
Bug 6513 First offset is good but second is bad -- didn't request task count. $ cat etc/job_submit.lua function slurm_job_submit(job_desc, part_list, submit_uid) slurm.log_user("submit1\nstuff") slurm.log_user("submit2") slurm.log_user("submit3") -- slurm.log_user("case 0") if job_desc.num_tasks == slurm.NO_VAL or job_desc.num_tasks == nil then slurm.log_user("Batch submit error: Must specify either number of nodes or number of tasks!") -- reject the job return slurm.ERROR end return slurm.SUCCESS end function slurm_job_modify(job_desc, job_rec, part_list, modify_uid) slurm.log_user("modify1") slurm.log_user("modify2") slurm.log_user("modify3") return slurm.SUCCESS end slurm.log_user("initialized") return slurm.SUCCESS $ sbatch -Ablah2 -n1 --wrap="hostname" : -J asdfl sbatch: error: 0: initialized sbatch: error: 0: submit1 sbatch: error: 0: stuff sbatch: error: 0: submit2 sbatch: error: 0: submit3 sbatch: error: submit1 sbatch: error: stuff sbatch: error: submit2 sbatch: error: submit3 sbatch: error: Batch submit error: Must specify either number of nodes or number of tasks! sbatch: error: Batch job submission failed: Unspecified error $ sbatch -Ablah2 -n1 --wrap="hostname" : -J asdfl sbatch: error: 0: initialized sbatch: error: 0: submit1 sbatch: error: 0: stuff sbatch: error: 0: submit2 sbatch: error: 0: submit3 sbatch: error: 1: submit1 sbatch: error: 1: stuff sbatch: error: 1: submit2 sbatch: error: 1: submit3 sbatch: error: 1: Batch submit error: Must specify either number of nodes or number of tasks! sbatch: error: Batch job submission failed: Unspecified error srun already handles this
-
Nate Rini authored
Was dumping this: $ srun -A test7.21-account.1 --qos test7.21-qos.1 -n5 : -n3 : -n1 /bin/true srun: error: 0: submit1 srun: error: submit2 srun: error: submit3 srun: error: Unable to allocate resources: Invalid account or account/partition combination specified Will now dump this: $ srun -A test7.21-account.1 --qos test7.21-qos.1 -n5 : -n3 : -n1 /bin/true srun: error: 0: initialized srun: error: 0: submit1 srun: error: 0: submit2 srun: error: 0: submit3 srun: error: Unable to allocate resources: Invalid account or account/partition combination specified Bug 6513.
-
Nate Rini authored
Bug 6895.
-
Brian Christiansen authored
Bug 6895
-
Brian Christiansen authored
Bug 6895
-
Danny Auble authored
-
- 26 Apr, 2019 9 commits
-
-
Marshall Garey authored
Bug 6215
-
Marshall Garey authored
Change references to the "micro" release in rpc.html and troubleshoot.html as well; SchedMD refers to the last part of the version number as the "maintenance" release. Bug 6833.
-
Alejandro Sanchez authored
Bug 6832.
-
Nate Rini authored
Bug 6832.
-
Nate Rini authored
Bug 6832.
-
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
-