isn't a sub-block job.

the XML.

Fix for bug 258

This fixes a bug introduced in commit f1cf6d2d
Without this change, a job with a partition related reason for not running
(e.g. MaxNodes) plus some other reason (e.g. dependency), could after satisfying
the second reason (e.g. dependency), have the select_nodes() function executed
and return SUCCESS on an allocation request, but it would not actually be
allocation resources since select_nodes() would interpret the request as a
test to see if it could ever run (e.g. will_run).
Bug 263

This logic strips leading zeros off node IDs for use with the aprun
-L option. Without this change, the node IDs with leading zeros are
interpretted as octal.
Partial fix for bug 260.

never looked at to determine eligibility of backfillable job.

and when reading in state from DB2 we find a block that can't be created.
You can now do a clean start to rid the bad block.

the slurmctld there were software errors on some nodes.

without it still existing there.  This is extremely rare.

a pending job on it we don't kill the job.

while it was free cnodes would go into software error and kill the job.

Fix for bug 224

WIthout this patch, when the slurmd cold starts or slurmstepd
terminates abnormally, the job script file can be left around.
bug 243

Previously such a job submitted to a DOWN partition would be queued.
bug 187

Fix spank_option_getopt in local context

In local context (srun, sbatch, salloc), spank_option_getopt() would
always return that an option was found due to a missing check for
spopt->found in spank_option_getopt.

This patch fixes the issue.

slurm.schedmd.com