Fix Version/s: None
Mock-based testing of pipeline_driver.py has run into several problems, including over-dependence on ctrl_mpexec. It would be cleaner to create a mock pipeline whose tasks do no processing besides creating output datasets. Implement such a pipeline and use it in tests that currently try to mock the pipeline, its executor, or pipeline_driver.
Note that ap_verify currently does some run-time configuration of the AP pipeline (e.g., database location), so the mock pipeline needs to have at least some of the same configuration hooks as the real pipeline. Also, since tasks must be importable to be included in a pipeline, they will need to go somewhere in the main python directory of ap_verify.
DM-33734 Investigate non-processing AP pipeline overhead
- has to be done after
DM-26140 Centralize Gen 3 pipeline configuration info for ap_verify datasets
Looks good, few minor comments for ap_verify.