- 15 Jan, 2019 14 commits
-
-
Morris Jette authored
Slurmd was generating errors of this sort for all GRES: error: Ignoring gres.conf record, invalid name: mps This was due to some GRES setup logic not being invoked on the slurmd. In any case, the relevant checking now only happens on the slurmctld.
-
Morris Jette authored
-
Morris Jette authored
If a gres type was identified in the node's GRES field, but that type was not listed in the slurm.conf GresTypes parameter then those GRES would appear in the output of "scontrol show node". This misleading/wrong information would cause a bunch of tests to fail. This patch only moves valid node GRES into the node record and deletes the rest.
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
This logic supports different MPS counts on each device, which is possible on a heterogeneous system
-
Morris Jette authored
-
Morris Jette authored
This prints GRES configuration information and exits. For testing.
-
Morris Jette authored
Needed for testing of gres/mps allocations
-
Morris Jette authored
Fix formatting and typo in log message
-
Morris Jette authored
Wrong variable name used
-
Morris Jette authored
This works for heterogeneous systems, various Counts for each GPU type, steps which use a subset of the job's gres/mps allocation, etc.
-
- 14 Jan, 2019 8 commits
-
-
Isaac Hartung authored
Bug 4700. Co-authored-by:
Tim Wickberg <tim@schedmd.com>
-
Tim Wickberg authored
Bug 6311.
-
Broderick Gardner authored
Silences this useless warning: ar: `u' modifier ignored since `D' is the default (see `U') Bug 6209.
-
Morris Jette authored
convert src/common/gres.c logic to use new suffix_mult() function in src/common/slurm_protocol_defs.c to parse numeric sufficies (GB, MB, etc.). No change in functionality.
-
Morris Jette authored
possibly needed to update a partition's total TRES counts when updating a node's GRES counts
-
Morris Jette authored
-
Morris Jette authored
-
Felip Moll authored
This patch removes the MemLimitEnforce parameter from Slurm and moves the condition to enable the feature to the JobAcctGatherParam=OverMemoryKill. Setting OverMemoryKill will now enable the mechanism that was before enabled with MemLimitEnforce=yes, so activation of killing jobs or steps due to exceeding memory will be done in the same place. Also reconfiguring or starting slurmd/ctld with incorrect configuration will cause a fatal error. Bug 5479
-
- 13 Jan, 2019 1 commit
-
-
Morris Jette authored
Redundant logic committed in 62e378a4 bug 6337
-
- 12 Jan, 2019 3 commits
-
-
Tim Wickberg authored
-
Morris Jette authored
-
Morris Jette authored
this fixes bug introduced in commit 4facada1 when a job was submitted with a valid gres name but count of zero
-
- 11 Jan, 2019 11 commits
-
-
Morris Jette authored
We decided with AMAT to remove gres/mps percent specification.
-
Michael Hinton authored
Add a debug statement. Bug 5823
-
Michael Hinton authored
When the backup slurmdbd is active, there is no need to print connection errors every 10 minutes when the backup checks in on the primary, at least at the 'error' level. Prevent dbd clients, like sacctmgr, from printing a connection error when running commands against the backup slurmdbd unless debug2. Before, the clients would always print errors when trying to access the primary dbd first. Bug 5823
-
Marshall Garey authored
The GRES Links info was added to v18.08, but the unpack was missing that field in v19.05. bug 6337
-
Morris Jette authored
Issuing job cancel on the wrong job ID. Also increase sleep in a test to better try to overlap the jobs.
-
Morris Jette authored
Support GRES types that include numbers (e.g. "--gres=gpu:123g:2"). Also change number suffix processing to use common function See commit 396e82a167 bug 6345
-
Morris Jette authored
See commit 396e82a167 bug 6345
-
Morris Jette authored
See commit 396e82a167 bug 6345
-
Morris Jette authored
Based on logic previously in src/plugins/burst_buffer/common/burst_buffer_common.c bug 6345
-
Michael Hinton authored
If a Unix socket path exceeds the limit, emit errors and exit. Fix memory leak on socket() failure. Bug 5386
-
Felip Moll authored
Fix issue introduced in commit 164d4878 that avoided a job to be modified setting the current reservation to none. Bug 6309
-
- 10 Jan, 2019 3 commits
-
-
Morris Jette authored
-
Morris Jette authored
Need to easily detect real memory leaks
-
Morris Jette authored
-