-
Notifications
You must be signed in to change notification settings - Fork 169
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
JP-3268: Fix pixel_replace step status error #7619
Conversation
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #7619 +/- ##
=======================================
Coverage 76.61% 76.61%
=======================================
Files 456 456
Lines 36819 36819
=======================================
Hits 28209 28209
Misses 8610 8610
*This pull request uses carry forward flags. Click here to find out more.
☔ View full report in Codecov by Sentry. |
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.
lgtm
🙈 |
regtest run intentionally used CRDS_TEST, which contains an updated pars-spec2pipeline ref file for MIRI LRS that turns on the pixel_replace step. The LRS tests show that the S_PXREPL keyword is now present and populated. All other failures are due to the differences in ref files in CRDS_TEST vs. CRDS_OPS (which is what the truth files are based on). So this looks good. |
Resolves JP-3268
This PR fixes the
pixel_replace
step code so that it properly updates the step status keyword on completion. Previously a data model object was being updated that was not the model returned from the step, so the update was lost.Checklist for maintainers
CHANGES.rst
within the relevant release sectionHow to run regression tests on a PR