-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-48044: Test subset definitions in ap_pipe pipeline tests #216
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Handful of comments, mostly clarifications of test docs and/or intent. In general, this seems like a good approach, and it looks like it caught a few incomplete pipeline definitions.
Thanks for using subTests! That should make debugging test failures much easier.
While you're in here: there's a bunch of extra spaces after mpSkyEphemerisQuery
in the generic ApPipe.yaml
(my editor highlights whitespace at the end of lines).
"""Test that instrument-specific pipelines have all the subsets of their | ||
generic counterparts. | ||
|
||
Note that this does not check inheritance *within* `_ingredients`! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to be explicit?
Note that this does not check inheritance *within* `_ingredients`! | |
Note that this does not check inheritance *within* `_ingredients/`! |
I don't remember why I recommended using `processCcd` here, but it's surprising behavior, and will make less sense once we remove ProcessCcd.yaml.
These subsets have never been needed (these pipelines are an implementation detail of DECam/ProcessCcd.yaml), but I can't find a good a priori reason why they should have an exception in the pipeline tests.
These tests verify our de-facto conventions for AP pipelines, but try to avoid hardcoding which tasks must be associated with which subsets.
These subsets were previously documented only in an RFC, but they're a key part of the interface that Prompt Processing uses to run the pipeline.
ddcc95c
to
5eae529
Compare
This PR fixes outstanding issues with subset definitions, and adds unit tests to check the more mechanical ones.