getStatus just reports a threadName. It should also indicate whether task had been created, and whether it is considered cancelled or done.
In principle a call to stop after start but before the task starts running could result in a hung step. This would normally be a very short interval, though, since the thread pool is unbounded. Could be made more robust.
|Summary||Strengthen AbstractSynchronousNonBlockingStepExecution.getStatus||Strengthen SynchronousNonBlockingStepExecution.getStatus|
|Remote Link||This issue links to "CloudBees Internal OSS-1614 (Web Link)" [ 18626 ]|