in the current directory but not in the --chdir specified cwd.

Now srun looks for the command in specified cwd and differentiates all
the possible cases where a command starts with ./ (relative), with /
(absolute), and with a different char indicating a command that is in
the path.

Fix also for a PATH variable starting by '.', now it is relative to
specified cwd.

bug 4392

Fix job array dependency with "aftercorr" option and some task arrays in
    the first job fail. This fix lets all task array elements that can run
    proceed rather than stopping all subsequent task array elements.
Bug 4590

Creating a copy of the actual environment in env->env defines a new pointer,
then next call to setup_env and setenvf doesn't define variables in the global
environment but in this new copy.

Bug 4615

 -- node_features plugin - Add suport for XOR & XAND of job constraints (node
    feature specifications).
 -- Add support for parenthesis in a job's constraint specification to group
    like options together. For example
    --constraint="[(knl&snc4&flat)*4&haswell*1]" might be used to specify that
    four nodes with the features "knl", "snc4" and "flat" plus one node with
    the feature "haswell" are required.

node_feature/knl_cray - Fix memory leak that can occur during normal
    operation. This will happen when an update request for a specific
    node happens.

If CnselectPath and/or SyscfgPath defined in knl_cray.conf file and
  slurmctld reconfigured, the original values of those paraemters
  would be over-written and their memory leaked.

Use FREE_NULL_BUFFER instead, otherwise we could attempt to
free_buffer a second time if we jump to the rwfail label.

bug4491

to preempt other eligible jobs.

Bug 4279

Missing from 390da8cf

Bug 4595

Bug 4127

When --mail-type option isn't requested with ARRAY_TASKS, we need somehow
to summarize the different states each task finished in the array. We've
added a new ARRAY_TASK_REQUEUED flag to the array_flags to indicate that
at least one task was requeued. Also the logic now detects if at least
one task failed and/or if otherwise all finished successfully.

The patch also removes the RunTime from the the e-mail when summarizing
whole array, since it doesn't make sense to specify just the RunTime
of one of the tasks for this case.

Patch also fixes when ARRAY_TASKS is specified, previously the mail
notification for the master job task record included a range of
ExitCodes for all the tasks. Since this option is not for summarizing,
the patch makes it so only the range is shown when the option isn't
specified.

Bug 4539.

Scheduling fix for changing node features without any NodeFeatures plugins.
Bug 4577

Bug 4448

Avoid setting node in COMPLETING state indefinitely if the job initiating
the node reboot is cancelled while the reboot in in progress. Bug
introduced in commit 7d246784

Bug 4536

Bug 4448

bug 4575

Add job state flag of "SIGNALLING" to avoid race condition with multiple
    SIGSTOP/SIGCONT signals for the same job being active at the same time.
bug 4531

Logic was backwards before.

Bug 4459.

Refactor logging logic to avoid possible memory corruption on non-x86
    architectures.
bug 4469

only affects current 17.11 users tracking licenses or GRES in the database.

Bug 4553

increment ids for the tres_table.

Bug 4553

Turns out auto_increment=# doesn't work in MySQL at the time of writing
but does work correctly in MariaDB >=10.2.4+

See bug for more information.

This reverts commit 12794fb0.

increment ids for the tres_table.

Bug 4553

Turns out auto_increment=# doesn't work in MySQL at the time of writing
but does work correctly in MariaDB >=10.2.4+

See bug for more information.

Bug 4555

Bug 4558.

to replace DOWN or DRAINED nodes.

Bug 4537

Bug 4566

Bug 4564

The ability to enforce strict content-type checking has existed since
Elasticsearch 5.3 via the http.content_type.required configuration setting.
In 5.x it is optional, and defaults to false, in Elasticsearch 6.0, that
setting defaults to true, and there is no way to disable it.

If required and not appended, Elasticsearch would response with status 406,
so "Content-Type: application/json" is appended from now on. Tested against
Elasticsearch 5.5.1 and 6.1.1.

Bug reported to slurm-users list from E.S. Rosenberg. Patch suggested didn't
check the return code of curl_slist_append() and didn't free the slist.