Story #18948

Container exit_code should be updated earlier, before copying staged outputs

Added by Tom Clegg about 2 months ago. Updated 19 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Crunch
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Currently crunch-run updates exit_code and output at the same time, when setting state=Complete -- in fact, RailsAPI doesn't allow updating exit_code until state=Complete.

This means that in the case where outputs are staged in the local filesystem, the exit_code is not propagated back to the database / other clients / users until after copying staged outputs to keep, which can take a while. During that interval, the exit code is shown in the log, but not in the container record.

If we adjust the RailsAPI constraint, and have crunch-run save the exit_code as soon as it's known, workbench2 and other clients can easily show this to the user earlier.

History

#1 Updated by Peter Amstutz about 1 month ago

I think the reason for the current behavior was that if you don't have the outputs, the container isn't "finished". However we could relax the constraint so you can set the exit code but stay in Running state.

#2 Updated by Peter Amstutz about 1 month ago

  • Target version changed from 2022-04-27 Sprint to 2022-05-11 sprint

#3 Updated by Peter Amstutz 29 days ago

  • Target version changed from 2022-05-11 sprint to 2022-05-25 sprint

#4 Updated by Peter Amstutz 19 days ago

  • Target version changed from 2022-05-25 sprint to 2022-06-08 sprint

#5 Updated by Peter Amstutz 19 days ago

  • Target version changed from 2022-06-08 sprint to 2022-06-22 Sprint

Also available in: Atom PDF