Bug 5564

doesn't exist yet (seg fault), and will get blown away in a few lines
when _build_bitmaps() is called.  That function should set things up
correctly anyway.

(it was ever only called from read_config.c)

Bug 5547.

Bug 5547.

in the step record for usage.

Bug 5557

CID 187635

Bug 5094

Continuation of commit aab9c311

Bug 5453

Causes srun and sattach to fail on big endian platforms.

Bug 5556

Wrong author.

This reverts commit 392e7cfc.

a job with scontrol.

Bug 4964

instead of an int for protocol_version.

Continuation of 392e7cfc

Bug 5556

Bug 5556

not work when trying use sattach.

Bug 5556

to run the regression tests 24.* without changing that code since it links
directly to the priority plugin where that function isn't defined.

Bug 5558

Continuation of commit 21d2ab6e

With the change to use tres_usage_type's the stats coming back from the
extern step are initialized to INFINITE64 instead of 0's.

jobacctinfo_create() in _handle_stat_jobacct() initializes jobacct, but
since the job->task[i]->pid == -1, no stats are gathered and the clean
jobacct is returned.

Related commit: fa3a8ff1

Bug 5554

Most calling paths to job_signal() were sending in job_ptr->job_id alongside
uid 0. This bypasses the unneeded uid validation, and forces another lookup
through find_job_record() for a job_ptr we just dereferenced.

So - change the less-used job_signal() to job_signal_id(), promote
_job_signal to an extern taking that name over, and stop this whole
unnecessary extra set of lookup calls.

Break JobId=... out from this, and only print the StepId=... bit.
This allows us to use %pJ in several additional places, and follows
the newer formatting used elsewhere of JobId=... StepId=... .

Due to how this code works, the end result is admittedly a bit uglier,
but the end result as printed to the logs is preferrable.

Add xasserts() to crash development builds if the wrong struct
is fed in, and fall back to checking the field and returning 'CORRUPT'
if the magic value is not found for production builds rather than
print garbage (and risk an out-of-bounds memory access).

Set when step is created, xassert() when the step is being destroyed.