This is needed to properly enforce limits and account for usage.

Remove the 1024-character limit on lines in batch scripts, which was
causing long lines to be silently truncated. I noticed it when jobs were
getting created with fewer dependencies than specified.

Also increase the line length when showing job info.

No change in logic

sched/backfill: If a job can not be started within the configured
    backfill_window, set it's start time to 0 (unknown) rather than the end
    of the backfill_window.
bug 2100

If a pending job array has multiple reasons for being in a pending state,
    then print all reasons in a comma separated list.

Before:
             JOBID PARTITION     NAME     USER ST       TIME  NODES NODELIST(REASON)
       97354_[1-4]     debug      tmp    jette PD       0:00      1 (Resources)

After:
             JOBID PARTITION     NAME     USER ST       TIME  NODES NODELIST(REASON)
       97354_[1-4]     debug      tmp    jette PD       0:00      1 (Resources,JobHeldUser)

The tests were sometimes failing unless I gathered accounting
  data at more frequent intervals. This seems to work with default
  accounting collection intervals.

When extra pools were reported by Cray API, it was not multiplying
  the buffer count by granularity to get the total size, but was
  just getting the counts.

job's TimeLimit if the job did't request --time

Bug 2130

Move slurmctld mail handler to separate thread for improved performance.
Original logic did fork/exec without separate thread and if the
slurmctld memory size is huge, then the time required for fork()
to complete can be significant.
bug 2252

Avoid hard-link/copy of script/environment files for job arrays. Use the
    master job record file for all tasks of the job array.
back port of commit 41eead64
bug 2220

Refactor logic to synchronize active bach jobs and their script/environment
    files, reducing overhead dramatically for large numbers of active jobs.
backport of commit 41eead64
bug 2220

If a job can never be started due to unsatisfied job dependencies, report
    the full original job dependency specification rather than the dependencies
    remaining to be satisfied (typically NULL).
bug 2197

in use.

Conflicts:
	src/slurmctld/proc_req.c

_slurm_rpc_complete_job_allocation.

This is a rewrite of 438365ec which didn't catch the job_ptr wasn't
in a lock so the memory issue could still of existed.  This hopefully fixes
all the spots the job_ptr wasn't in the lock.

Fixes bug 2146

This reverts commit 438365ec.

Bug 2261

15.08.5.

Bug 2243

bug 2171

Decrease parallelism in job cancel request to prevent denial of service
    when cancelling huge numbers of jobs.
bug 2256

Prevent triggering gang scheduling within a partition if configured with
    PreemptType=partition_prio and PreemptMode=suspend,gang.
The essence of this fix is to change a "<=" to "<" in cons_res/job_test.c:
-               if ((p_ptr->part_ptr->priority <= jp_ptr->part_ptr->priority) &&
+               if ((p_ptr->part_ptr->priority < jp_ptr->part_ptr->priority) &&
but logic was also added to insure that a partition configuration with
PreemptMode did not override PreemptType != partition_prio.
bug 2232

No changes to logic

Previously an error() would be logged when the attempt to open the job
script using the new directory format failed but the successive fallback to the
old directory structure was successful, leading to confusion when troubleshooting.

Move emitted warnings to debug(), and only error() after failing to open in both
directory structures. Add a note about backwards compatibility to both functions -
we cannot remove these fallbacks as directory structure for pending jobs does not
change on Slurm version update, and people may need to chain multiple version
update together to get to a current slurm version which would correctly update
slurmctld state files but leave pending jobs in the old directory structure.

Bug #2244.

If a job is requeued while in the process of being launch, remove it's
    job ID from slurmd's record of active jobs in order to avoid generating a
    duplicate job ID error when launched for the second time (which would
    drain the node).
bug 2240