Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:
-
Story Points:1
-
Epic Link:
-
Sprint:AP S22-6 (May), AP F22-1 (June), AP F22-3 (August)
-
Team:Alert Production
-
Urgent?:No
Description
I found the --fail-fast option to pipetask, which causes the pipeline execution to fail immediately on error, instead of trying to continue execution. I think this is what we want for ap_verify, as it's purpose is to test our pipeline, and any failures should halt.
Adding `"--fail-fast",` to line 98 of ap_verify's pipeline_driver.py seems to have done the trick.
Alternately, we could make this a commandline option to ap_verify, if we don't want to always fail immediately (but I think we do?).
Attachments
Issue Links
- is triggered by
-
DM-34254 ap_verify metrics report 0 completeness after switch to Piff
- Done
I'm sorry, but I still don't understand what you are trying to do (with either change), so I don't believe I'm in a position to approve or disapprove. Perhaps Meredith Rawls has a better understanding of what this would mean for our workflows (if she's not too busy)?