- 17 Jul, 2018 2 commits
-
-
Felip Moll authored
Previously, slashes '\' in job->cwd were always expanded regardless of they were part of the name of a directory or not. Bug 4859
-
Felip Moll authored
When dealing with special characters like %A, %u, %s and so on and escaping it on the command line, problems arises when one have directories with multiple slashes in their names. This patch fixes this situation removing only one slash on each pair of slashes just as normal escaping works i.e. in bash. Bug 4859
-
- 12 Jul, 2018 3 commits
-
-
Boris Karasev authored
- avoid `abort()` when collective is failed - added logging of coll details for fail cases Bug 5067
-
Danny Auble authored
Note, this is setting it up so we can use defunct functions. It will probably need to be properly fixed in a future version so we don't do this.
-
Dominik Bartkiewicz authored
with preemption or when job requests a specific list of hosts. Bug 5293.
-
- 09 Jul, 2018 1 commit
-
-
Danny Auble authored
-
- 06 Jul, 2018 1 commit
-
-
Marshall Garey authored
Continuation of 923c9b37. There is a delay in the cgroup system when moving a PID from one cgroup to another. It is usually short, but if we don't wait for the PID to move before removing cgroup directories the PID previously belonged to, we could leak cgroups. This was previously fixed in the cpuset and devices subsystems. This uses the same logic to fix the freezer subsystem. Bug 5082.
-
- 05 Jul, 2018 1 commit
-
-
Danny Auble authored
the database. Bug 5247
-
- 04 Jul, 2018 2 commits
-
-
Morris Jette authored
So that multiple nodes changes will be reported on one line rather than one line per node. Otherwise this could lead to performance issues when reloading slurmctld in big systems. Bug4980
-
Felip Moll authored
Cleaned up code that could've caused performance issues when reading config and there was nodes with features defined. bug4980
-
- 03 Jul, 2018 2 commits
-
-
Broderick Gardner authored
bug 5337
-
Brian Christiansen authored
Currently, no caller checks the return code. Bug 5164
-
- 26 Jun, 2018 4 commits
-
-
Dominik Bartkiewicz authored
Some job fields can change in the course of scheduling. This patch reinitializes previously adjusted job fields to their original value when validating the job memory in multi-partition requests. Bug 4895.
-
Alejandro Sanchez authored
This reverts commit bf4cb0b1. Bug 5240, Bug 4895 and Bug 4976.
-
Felip Moll authored
When one asks for an inactive feature and also specifies the node with -w flag, the node will be rebooted despite it may contain running jobs. bug4821
-
Tim Wickberg authored
and avoid race condition calling task before proctrack can introduce. Bug 5319
-
- 25 Jun, 2018 1 commit
-
-
Morris Jette authored
delayed until the first job completes execution and it's burst buffer stage-out is completed. Bug 4675
-
- 22 Jun, 2018 2 commits
-
-
Morris Jette authored
If MailProg is not configured and "/bin/mail" (the default) does not exist, but "/usr/bin/mail" does exist then use "/usr/bin/mail" as a default value.
-
Dominik Bartkiewicz authored
Bug 5159.
-
- 20 Jun, 2018 2 commits
-
-
Morris Jette authored
-
Alejandro Sanchez authored
Previously the function was only testing against the first partition in the job_record. Now it detects if the job request is multi partition and if so then loops through all of them until the job will run in any or until the end of the list, returning the error code from the last one if the job won't run in any partition. Bug 5185
-
- 19 Jun, 2018 3 commits
-
-
Isaac Hartung authored
When requesting specific jobids with sacct, the starttime of the request is 0, which will cause the time range to be outside of the MaxQueryTimeRange range -- if specified. When requesting specific jobids, sacct should be able to find the job whenever it started -- unless confined to a smaller range with -S and/or -E. Bug 5009
-
Morris Jette authored
For heterogeneous job component with required nodes, explicitly exclude those nodes from all other job components.
-
Felip Moll authored
-
- 18 Jun, 2018 1 commit
-
-
Danny Auble authored
Specifically due to SELECT ... FOR UPDATE ones. Bug 5086.
-
- 15 Jun, 2018 2 commits
-
-
Marshall Garey authored
Bug 5270.
-
Tim Wickberg authored
Instead of unintentionally rejecting the update from a non-Administrator if the job_submit plugin modified that field. Bug 5306.
-
- 14 Jun, 2018 1 commit
-
-
Felip Moll authored
sched/backfill: Reset job time limit if needed for deadline scheduling. bug 5183
-
- 13 Jun, 2018 1 commit
-
-
Tim Wickberg authored
I do not see a use for this syntax, especially given that it appends an extra comma in between the two halves. Only allow the full string to change to put this in line with the Comment handling. Remove special handling of an identical AdminComment as well, since the end result is unchanged, and this avoids a potentially expensive xstrcmp call. Bug 5306.
-
- 12 Jun, 2018 3 commits
-
-
Danny Auble authored
-
Danny Auble authored
Bug 5286
-
Tim Wickberg authored
RHEL 6 (and related) use lua as the package name, test if that package exists with a version >= 5.1 if the other tests have already failed. Bug 5263.
-
- 10 Jun, 2018 1 commit
-
-
Dominik Bartkiewicz authored
bug 4987
-
- 08 Jun, 2018 2 commits
-
-
Tim Wickberg authored
And do not list each individual sensor reading but just the computed sum of each one grouped by key. Bug5274
-
Morris Jette authored
This is in anticipation of an upcoming change to the cgroup hierarchy on a future CLE release. Bug 5145.
-
- 07 Jun, 2018 2 commits
-
-
Brian Christiansen authored
If defined, is called when a node failes to resume by ResumeTimeout.
-
Isaac Hartung authored
if any task in the array was requeued. This is a hint to use "sacct --duplicates" to see the whole picture of the array job. Bug 5105
-
- 06 Jun, 2018 3 commits
-
-
Morris Jette authored
burst_buffer.conf - Add SetExecHost flag to enable burst buffer access from the login node for interactive jobs.
-
Alejandro Sanchez authored
And remove the initialization before all the calls to the function. It is non-functional and the motivation is more a preventive thing so that if we ever use slurm_mktime() we know tm_isdst is consistently set to -1. Bug 5230.
-
Brian Christiansen authored
which were marked down due to ResumeTimeout. If a cloud node was marked down due to not responding by ResumeTimeout, the code inadvertently added the node back to the avail_node_bitmap -- after being cleared by set_node_down_ptr(). The scheduler would then attempt to allocate the node again, which would cause a loop of hitting ResumeTimeout and allocating the downed node again. Bug 5264
-