Correction to hostlist parsing bug introduced in v2.6.4 for hostlists with
more than one numeric range in brackets (e.g. rack[0-3]_blade[0-63]").
bug505

Clear a job's core specialization option in select plugins that
we do not want to support the option (e.g. bluegene, alps, linear,
and serial). Only support it in cons_res and cray plugins (not yet
coded though).

Also correct test ID to be of the form #.#

Rather than directly referencing the individual headers in
src/common

plugin: rank map_cpu mask_cpu rank_ldom map_ldom mask_ldom boards.
All these options except "boards" are currently supported by
task/affinity. "boards" is a new option not previously supported.

Just a start for now

Conflicts:
	NEWS

Conflicts:
	META
	src/plugins/priority/multifactor/priority_multifactor.c

Avoid decrementing grp_used_cpu_run_secs if we are not enforcing
accounting limits. Without this change, the plugin will decrement
times from zero cpu used times (i.e decrement an uninitialized
variable).

Added -S/--core-spec option to salloc, sbatch and srun commands to reserve
    specialized cores for system use. Modify sview and scontrol to set/get
    core_spec
struct job_info / slurm_job_info_t: Added core_spec
struct job_descriptorjob_desc_msg_t: Added core_spec

Make HTML generator scripts Python 3 compatible

The system really can not handle larger job arrays without adding
a job array data structure, but this puts some of the infrastructure
in place now.

Disable test if FairShareDampeningFactor != 1

to offer a greater priority range based upon utilization.

Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423

Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423

Conflicts:
	NEWS
	contribs/torque/qsub.pl

Fix to work with change logic introduced in Slurm version 2.6.3
scheduling logic which prevented Maui/Moab from starting jobs.