Correct the job array specification parser to accept brackets in job array
expression (e.g. "123_[4,7-9]").
This patch superseeds patch 8d811201
bug 1552

The logic fails if there are commas in the brackets:
slurmctld: job_str_signal: 3 invalid job id 1593_[2,5-6]
Updated patch in next commit
bug 1552

RequeueExit and RequeueExitHold configuration parameters modified to accept
numeric ranges. For example "RequeueExit=1,2,3,4" and "RequeueExit=1-4" are
equivalent.
bug 1549

If SchedulerParameters value of bf_min_age_reserve is configured, then
a newly submitted job can start immediately even if there is a higher
priority non-runnable job which has been waiting for less time than
bf_min_age_reserve.

Start job allocation using lowest numbered sockets for block task
distribution for consistency with cyclic distribution.
bug 1540

block is set up to it's original state.

Bug 1533

Fix bug that can permit someone to kill job array belonging to another user.

Fix support for --mem=0 (all memory of a node) with select/cons_res plugin.
Previously the job would not have it's memory constrained, but it would not
make that memory unavailable to other jobs either.
bug 1526

This was previously added to v14.11

Added new SchedulerParameters value of bf_min_age_reserve. The backfill
scheduler will not reserve resources for pending jobs until they have
been pending for at least the specified number of seconds. This can be
valuable if jobs lack time limits or all time limits have the same value.

Increase maximum MaxArraySize configuration parameter value from 1,000,001
to 4,000,001.
bug 1535

Cray - Fix for launching batch step within an existing job allocation.
bug 1509

Partially revert commit 8d91ae22
The bug was introduced in version 14.11.0-pre4.
bug 1504

This is for bug 1514

before.

Bug 1507

message comes in

Bug 1501

cluster(s) requested.

Bug 1492

For job running under a debugger, if the exec of the task fails, then
cancel its I/O and abort immediately rather than waiting 60 seconds for
I/O timeout.

Bug 1476

Bug 1469

The /root/.my.cnf would typically contain the login credentials for
root.  If those are needed for Slurm, then it should be checking
that directory.

(In reply to Nina Suvanphim from comment #0)
...
> const char *default_conf_paths[] = {
> "/root/.my.cnf", <<<<<<<<<<<<<<<<<------- add this line
> "/etc/my.cnf", "/etc/opt/cray/MySQL/my.cnf",
> "/etc/mysql/my.cnf", NULL };

I'll also note that typically the $HOME/.my.cnf file would be
checked last rather than first.

don't support strong_alias