Bug 7861

Bug 7291

Bug 7291

In a multi-cluster environment a job may submit more jobs as part of
its workflow. This fixes situations where the variable is inherited
incorrectly on sub-jobs.

Bug 7998

srun waits for the prolog to finish before launching a job step.
In _is_prolog_finished(), slurmctld checks the state reason:

	if (job_ptr) {
		is_running = (job_ptr->state_reason != WAIT_PROLOG);
	}

But if the job is updated during the job prolog, then _update_job() will
change the state_reason, and then slurmctld will tell srun that the
prolog is completed even if it isn't. If srun launches a job step before
the extern sets up x11, then the job step won't have x11 information. To
fix this, don't change state_reason in _update_job() if it equals
WAIT_PROLOG.

Bug 7525

This in turn fixes allocation requests that weren't rejected and they
should because the requested nodes didn't have a shared network.

Bug 8210

Bug 8047

Bug 7766

Add <p> after <pre> tags, since <pre> breaks the previous <p>.
Add <p> and list tags where appropriate for correct spacing.
Replace < and > with escape characters in code snippets.
Fix some broken tags.

Bug 7308

Change prompts to "$ ".

Bug 7308

Bug 7308

Bug 7308

Bug 7308

Bug 7308

Bug 7308

Bug 7308

Bug 7308

Bug 7308

Bug 7308

# Conflicts:
#	testsuite/expect/test34.2

Have the main scheduler and backfill scheduler make the reasons of
subsequent array tasks match the first array task, since they
sometimes didn't do this completely when the array was pending.

Bug 6814

It is possible there may be an infinite loop when placing tasks when
_at_tpn_limit() activates on every possible node. If that happens, then
the job can not be placed and an error will be returned instead.

Continuation of 16eb8b14

Bug 7629.

Add _at_tpn_limit() as helper to determine when a given node is over the
tasks_per_node limit and to log when then happens.

Bug 7629.

Option may be useful when running --stop-on-first-fail,
when the issue is fixed than it will allow restart from
the failed one.

Bug 7433.

Bug 7274

Test regression bug 7378, commit 1c051c61.

Bug 7624.

Signed-off-by: Jason Booth <jbooth@schedmd.com>

Bug 7189

Increase the sleep in job to 5s was required to make test reliable. It
doesn't result in longer execution since we're waiting for job to get
into RUNNING state and then we're canceling it. Short sleep can end-up
with overlook of RUNNING state and false negative result - 'Job is DONE
but expected RUNNING'.

Bug 7624.

Previously there were no log_error before setting exit_code to 1
due scontrol error.
Now user can identify the reason of final FAILURE result.

Bug 7624.