-
Notifications
You must be signed in to change notification settings - Fork 6
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-42127: Add htcondor support for bps report --return-exit-codes #161
Conversation
The GenericWorkflow class has a property which provides the job count per task label. Made changes to ensure that the label ordering reflects the ordering of the pipetasks in the pipeline.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #161 +/- ##
==========================================
- Coverage 78.47% 78.44% -0.04%
==========================================
Files 40 40
Lines 3108 3099 -9
Branches 530 529 -1
==========================================
- Hits 2439 2431 -8
Misses 578 578
+ Partials 91 90 -1 ☔ 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.
One efficiency question and a minor comment change. Merge approved.
@@ -284,7 +284,7 @@ def compile_job_summary(jobs): | |||
|
|||
Parameters | |||
---------- | |||
jobs : `list` [`lsst.ctrl.bps.WmsRunReport`] | |||
jobs : `list` [`lsst.ctrl.bps.WmsJobReport`] | |||
List of run reports. |
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.
If changing type to WmsJobReport, then should the comment be "List of job reports."?
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.
Yes, it should. Will fix.
Previous version of the ExitCodesReport was assuming that the payload (pipetask) always exits with exit code 1 if case of any error. As a matter of fact, the pipetask can also exit with code 2 when any issues with the command line are encountered (e.g. bad command, option, etc.). Hence I added additional column to the exit code report which, similarly to infrastructure errors, will show what type payload errors happened during pipeline execution.
e39a22d
to
45fa4b3
Compare
Updated pre-commit config file to use the most recent Black.
45fa4b3
to
db93175
Compare
Checklist
doc/changes