Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ctrl_mpexec
-
Story Points:1
-
Epic Link:
-
Sprint:DB_S22_12
-
Team:Data Access and Database
-
Urgent?:No
Description
It looks like pipetask, when run with -j1, always stops after the first failed task instead of trying to execute other tasks (as if --fail-fast option was given). Should be easy to fix.
Michelle Gower, do you want to review this ticket? Changes are reasonably small. I don't think that change in exception handling has any effect on BPS, let me know if it can be an issue.