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
Implemented option to run jobs in parallel for PV validation #24906
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24906/6875 |
A new Pull Request was created by @cardinia for master. It involves the following packages: Alignment/OfflineValidation @cmsbuild, @franzoni, @pohsun, @tocheng, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins. |
if self.NJobs > 1: | ||
raise AllInOneError("Parallel jobs not implemented for the PrimaryVertex validation!\n" | ||
"Please set parallelJobs = 1.") | ||
# if self.NJobs > 1: |
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.
@cardinia why keep the commented out lines?
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.
@mmusich , they can be removed without problems. I initially thought that keeping them could be useful when working on the Parallel Validation code itself to loosen some of the current limitations (number of jobs to be sent in parallel or the need to specify the maximum number of events). But that was just a thought, their usefulness is basically none, I can remove those lines without problems.
Comparison job queued. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24906/6881 |
Comparison is ready Comparison Summary:
|
@smuzaffar not sure why the status of test and comparison was not updated |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
Comparison job queued. |
@fabiocos , PR was updated that is why test and comparison signatures were sent to pending. |
Comparison is ready Comparison Summary:
|
+1 |
@connorpa
Option for running jobs in parallel for the Primary Vertex Validation implemented and tested as discussed in Tracker Alignment meeting (https://indico.cern.ch/event/750047/#35-parallelisation-of-validati)