If the highest priority job is a job array which can not start
additional tasks due to the task count limit, do not let that
job prevent the initiation of lower priority jobs.

message opcode for easier debug.

Append subsystem name to cgroup mountpoint path extracted from
configuration file cgroup.conf. Without this patch, the script does
not execute properly and some garbage is let in cgroup filesystems.

Not a bug but a cosmetic patch to avoid double definition of variable
rmcg and uidcg.

Without this change, if the last task of a job array is started, then requeued, it will appear twice in the job array hash table, which typically results in a linked list that loops back on itself (an infinite loop)

Without this change, canceling the last task of a job array while pending could result in a fatal error due to NULL bitmap value

so when task_id_str is made we update the record in the database.

Wait up to 20 seconds for gres.conf file before exiting.

This fixes some problems creating advanced reservations on heterogeneous systems, especially when core counts are specified in the reservation.
bug 1068

Previous test used /tmp for creating stdout/err files. If files
are left from a previous test by another user, the test would
always fail. It was also necessary to increase the field size
logged for checking since the current working directory might
be a long path.

job_ptr is really the already existing job_ptr minus the task that was
just scheduled.

job_ptr's db_index was reset.

Make "srun --gres=none ..." work when executed without a job allocation
(i.e. srun creates the allocation plus the step). Previous logic would
try to create the job with a gres value of "none".

Fix for possible error if job has GRES, but the step explicitly requests a
GRES count of zero.

BlueGene/Q's runjob command requires a fully qualified pathname,
so only for that machine type, resolve the name in srun. This
partitially reverts commit 57efc873
but only for BGQ systems.

Each node was logged loaded to the layouts table was being logged
using debug(), which produces a great number of messages with
minimal value. I changed the message to debug3() and moved it
in the code so it would not be generated when an error() message
is also generated.

If this failed previously, it would leave an open file descriptor
and pass that to spawned applications without logging anything.
However, test7.9 would fail.

bug 754

There was bad logic if an update was being performed on multiple tasks
of a job record resulting in a fatal error.

works for update, hold, release, suspend, resume, requeue and
requeuehold operations