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

Also fix a tests so that multiple nodes are not required.

The data could be purged after job completion

The json m4 script has a bad variable name.

The power consumption threasholds are percentages, so they needed
  to be divided by 100 for proper use.

Intervals below 10 seconds on a Cray system will occasionally
  result in making scheduling decisions based upon old power
  consumption data. May even require larger values for larger
  systems.

Added LaunchParameters configuration parameter. Have srun command test
locally for the executable file if LaunchParameters=test_exec or the
environment variable SLURM_TEST_EXEC is set. Without this an invalid
command will generate one error message per task launched.

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

Change check of batch step ID from NO_VAL to SLURM_BATCH_SCRIPT
  for better consistency.

Conflicts:
	src/slurmd/slurmstepd/task.c
	src/squeue/print.c

This should not be a problem in v14.03, but the logic will be
  important in v14.11 due to larger job arrays being supported.

Make sure variables are initialized before passing a pointer to
  them as a function argument. The variable is set in the underlying
  function, so this is mostly cosmetic.

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

Also replaces some spaces with tabs.
bug 1354

Add new configuration parameter "set_watts" to explicitly set every
  node's power cap to the same value.
Improve accuracy of power cap data logging.
Fix logic for changing configuration values with SIGHUP or
  "scontrol reconfig" command.
Correct power distribution calculation.

Restores same behavior prior to ce32018a.
Bug 1513

A fairly major update to use JSON data strurctures directly to set
  power caps for better scalability and performance.
Added logic to send STDIN to the capmc command (with the JSON data).

This is for bug 1514

Relocate where power plugin is told about new job allocation.
Previous logic failed to work for job allocated resources at
submission time (top priority job does not need to go through
the same job scheduling logic as jobs that are already in the
queue, and thus failed to notify the power plugin at start time).

before.

Bug 1507