Tests that submit jobs via JobClient hang until they are killed if something goes wrong in the back end -JobClient does not impose limits on how long runs should take, but JUnit does. If we had an overload of runJob() that took a timeout, JobClient could kill a job that was taking too long, extracting the stack trace and better diagnostics to the test reports.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1936d 23h 20m||1||Steve Loughran||03/Mar/14 10:07|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||2.2.0 [ 12325050 ]|
|Resolution||Cannot Reproduce [ 5 ]|
|Field||Original Value||New Value|
|Assignee||Steve Loughran [ steve_l ]|