Force job status to ERROR
|Reported by:||Nicklas Nordborg||Owned by:||everyone|
In some cases a job crashes without updating the status in BASE. For example, I had a recent crash of the database and everything just freezed and Tomcat and the database had to be restarted. The running jobs were left in EXECUTING state. The "Abort" button could be used to put the jobs in ABORTING state but since they were not actually running they never reached the final ERROR state.
There is also this case: http://baseplugins.thep.lu.se/ticket/758
It would be nice to be able to forcibly set the status of a job to ERROR.