Project

General

Profile

Actions

Idea #18948

closed

Container exit_code should be updated earlier, before copying staged outputs

Added by Tom Clegg about 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Crunch
Target version:
Start date:
06/24/2022
Due date:
Story points:
-
Release relationship:
Auto

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.


Subtasks 1 (0 open1 closed)

Task #19210: Review 18948-update-exit-code-earlyResolvedLucas Di Pentima06/24/2022Actions
Actions

Also available in: Atom PDF