Story #18948
closedContainer exit_code should be updated earlier, before copying staged outputs
100%
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.
Updated by Peter Amstutz over 2 years 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.
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-04-27 Sprint to 2022-05-11 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-05-11 sprint to 2022-05-25 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-05-25 sprint to 2022-06-08 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-06-08 sprint to 2022-06-22 Sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-06-22 Sprint to 2022-07-06
Updated by Tom Clegg over 2 years ago
- Status changed from New to In Progress
18948-update-exit-code-early @ 40dc04d6fa45b6b727e94986491c06132db4a582 -- developer-run-tests: #3192
Updated by Tom Clegg over 2 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados-private:commit:arvados|47e929743cefd13760b9c84e1c148115aa3fc96c.