- 06 Mar, 2018 20 commits
-
-
Bill Brophy authored
Not sure if this could be done a different way. At the moment I wouldn't mind making a filesystem specific structure to pass in. Or perhaps make use of a different array or such. In the end this might be the best way to do it, but it isn't clear at the moment since the num_* isn't sent to the database in any fashion. Bug 2782
-
Bill Brophy authored
This will most likely be reverted as well since we plan on moving the Usage TRES to dynamic. Bug 2782
-
Bill Brophy authored
At the moment I am wondering if this is needed or not. Perhaps we might want to revert this. Bug 2782
-
Bill Brophy authored
Bug 2782
-
Bill Brophy authored
Bug 2782
-
Bill Brophy authored
Bug 2782
-
Danny Auble authored
-
Bill Brophy authored
TRES. This will hopefully be reverted in the future when TRES information is returned from the slurmd. Bug 2782
-
Bill Brophy authored
-
Danny Auble authored
-
Bill Brophy authored
Bug 2782
-
Bill Brophy authored
char * nodelist. Bug 2782
-
Bill Brophy authored
Bug 2782
-
Bill Brophy authored
Bug 2782
-
Bill Brophy authored
the future. Bug 2782
-
Danny Auble authored
to get ready for additions. Hopefully no code change Bug 2782
-
Bill Brophy authored
Bug 2782
-
Bill Brophy authored
Bug 2782
-
Bill Brophy authored
Bug 2782
-
Morris Jette authored
Log the option is not supported using info() message: $ sbatch -I tmp sbatch: --immediate option is not supported for the sbatch command, ignored Submitted batch job 1234
-
- 02 Mar, 2018 1 commit
-
-
Felip Moll authored
'sacctmgr show accounts withassoc cluster=x' now behaves like 'show users' displaying always all the accounts on the enterprise. Non-matching filtered account is now just displayed without associations. Bug 4804
-
- 01 Mar, 2018 3 commits
-
-
Felip Moll authored
When Cray NHC is stuck for a job for more than 300 seconds and a reconfigure is issued, job resources will be released in order to not keep all the job nodes allocated when there's no reason to. If then NHC finishes, resources will be released again causing memory under-allocated errors. This patch avoids releasing resources more than one time. Bug 4801
-
Dominik Bartkiewicz authored
reference commit 08425d9c
-
Tim Wickberg authored
-
- 28 Feb, 2018 6 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
Update slurm.spec and slurm.spec-legacy as well
-
Isaac Hartung authored
Also throws spurious errors of: "slurmd: error: Domain socket directory /var/spool/slurmd: No such file or directory" if you SlurmdSpoolDir is located elsewhere. Bug 4289.
-
Dominik Bartkiewicz authored
Add additional protection in slurmctld as well. Bug 4826.
-
Alejandro Sanchez authored
job_limits_check() uses the job desc to call _valid_pn_min_mem(). This second function might adjust the following values (up to date): cpus_per_task pn_min_memory min_cpus max_cpus pn_min_cpus If the function returns success, these adjusted members need to be copied back to the job_record. It turns out pn_min_cpus wasn't copied back, thus the logs claimed to automatically increase pn_min_cpus but actually the job record wasn't modified and the select plugin tried to allocate wrong amount of resources. Bug 4823.
-
Tim Wickberg authored
Bug 4741.
-
- 27 Feb, 2018 2 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
No longer needed, and will cause errors on FreeBSD systems build with WITHOUT_KERBEROS. Bug 4805.
-
- 26 Feb, 2018 1 commit
-
-
Morris Jette authored
Relatively minor changes to burst_buffer/cray in preparation for support of #DW create_persistent and #DW destroy_persistent operations
-
- 23 Feb, 2018 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
Bug 4783
-
- 22 Feb, 2018 5 commits
-
-
Morris Jette authored
"#DW destroy_persistent" directives available in Cray CLE6.0UP06. This will be supported in Slurm version 18.08. Use "#BB" directives until then. Bug 4302
-
Morris Jette authored
-
Felip Moll authored
Fix missing rename of functions.
-
Felip Moll authored
-
Felip Moll authored
Only a single io_timeout_thread should be created for each sls struct. Creating multiple, while seemingly harmless in operation, can lead to fatal() messages when srun shuts down by destroying mutex locks that are in use by threads that srun doesn't expect to still have running. Regression caused by a1185f04. Bug 4596
-