[ET Trac] [Einstein Toolkit] #1286: SimFactory should not run queued chained jobs if a previous job fails

[Einstein Toolkit]

#1286: SimFactory should not run queued chained jobs if a previous job fails
--------------------------+-------------------------------------------------
  Reporter:  hinder       |       Owner:  eschnett
      Type:  enhancement  |      Status:  new     
  Priority:  major        |   Milestone:          
 Component:  SimFactory   |     Version:          
Resolution:               |    Keywords:          
--------------------------+-------------------------------------------------

Comment (by eschnett):

 That may be too simplistic. If a simulation runs out of queue time, would
 that count as "success"? Would you expect Simfactory to continue chaining
 jobs in this case? What if different MPI processes return different exit
 codes? What is, in general the exit code of mpirun anyway? What would you
 do if a simulation runs of of time? out of memory? out of disk space? What
 if there is a file permission error and the simulation can't write? What
 if the Cactus executable never actually starts because something is wrong?
 What if the user used qdel to stop a simulation? What if the user used
 qdel to stop a simulation? What if the user used the web interface or a
 termination trigger to stop the simulation?

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1286#comment:3>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit