Bug 4274

Verify that a tres weight is an integer.

This allows job limits to be enforced at submission -- with QOS
DenyOnLimit flag. Note that the values could be expanded at schedule
time (e.g. request one task but get all cpus on a core). The expanded
values are considered when scheduling.

Cont. Bug 4274

Cont. Bug 4274

being able to be set/updated on a partition.

Bug 4274

Bug 4274

Bug 5103

Bug 5103

Bug 5103

# Conflicts:
#	src/slurmctld/job_mgr.c

Can lead to deadlock within malloc depending on the exact timing.

Rework thread startup and shutdown code so pthread_cancel is not
needed.

Bug 5119, 5103.

happens.

Bug 5108

This reverts commit de5a4da2.

happens.

Bug 5108

Turns out the partititon's billing tres was working off the sum of
the node_ptrs which contain the max of all partitions they are in.

This isn't correct since each partition's billing can be different.

Set it correctly here.

Noticed while auditing use of pthread_cancel.

This is a followup to the last commit.

thread.

Otherwise you could get into a race where we don't have it running
when the registration response is sent back which now leads us to not
have any TRES to send to the slurmstepd.

This will give us debug before we had it before.  I see no reason to
delay it until later.

We found on most systems we would only need to wait < 20000 usecs for
this to happen.  This is much shorter of a time than the before 1 sec.
We found we almost always (100% from my testings) for the step to finish
in the first place though.

No functional change.

The use in _watch_tasks needs to be removed as the switch to pthread_signal
from pthread_cancel means this will not get interrupted and would keep the
step alive for at least a second, potentially harming throughput.
Since the call to _poll_data() happens after the first timer expires,
this delay turns out to be unnecessary, so we won't be replacing it with
a pthread_cond_timedwait() construct.

The use jobacct_gather_stat_task() is unnecessary since the two locations
this can happen take place after _fork_all_tasks() has setup the tasks,
thus the delay should not be necessary.

Bug 5103.

These functions are not async-cancel-safe, and cannot safely be cancelled.
This leads to potential deadlock, either between our own locks, or deep
inside glibc when the thread held a malloc arena lock when canceled.

Replace with pthread_signal to the appropriate cond to
wake threads up at the appropriate time instead.

Bug 5103.

This will make it easier in a future commit to avoid the
async pthread_cancel.

Bug 5103

Bug 5110.

# Conflicts:
#	src/slurmctld/job_mgr.c

Remove partition MaxTime limit at the beginning of the test,
run the rest of the test, then restore the partition configuration
with scontrol reconfigure.

Bug 4994.

Otherwise the extern step will disappear after 11.5 days.

Bug 5000.

to be sure if it is created under job write lock.

Bug 4901