WorkflowRunRestartTest.resumeDisabled should not assume that the execution is not loaded

[jglick]

From #159 I see an apparent mistake in #93. The execution is indeed loaded after a restart:

java.lang.Exception: Stack trace
	at java.lang.Thread.dumpStack(Thread.java:1336)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:711)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:957)
	at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65)
	at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57)
	at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
	at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
	at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178)
	at jenkins.model.Jenkins.<init>(Jenkins.java:989)
	at …

which does not seem improper. The test may have passed accidentally due to a race condition with the restart.

[dwnusbaum]

Should we invert the assertion instead of deleting it? Would pulling in jenkinsci/jenkins-test-harness#210 make the behavior consistent?

[jglick]

Should we invert the assertion

Not sure I see the point.

Would pulling in jenkinsci/jenkins-test-harness#210 make the behavior consistent?

Not sure.