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
[TkAl] Update PV Validation and PV Resolution per-run submission tools #31694
[TkAl] Update PV Validation and PV Resolution per-run submission tools #31694
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31694/18847
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages: Alignment/OfflineValidation @yuanchao, @christopheralanwest, @tocheng, @cmsbuild, @tlampen, @pohsun 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.
|
-1 Tested at: 500a29e CMSSW: CMSSW_11_2_X_2020-10-06-2300 I found follow errors while testing this PR Failed tests: UnitTests
I found errors in the following unit tests: ---> test testAlignmentOfflineValidation had ERRORS |
Comparison job queued. |
@cmsbuild, please test |
The tests are being triggered in jenkins.
|
Comparison is ready Comparison Summary:
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The aim of this PR is to update the Tracker Alignment PV Validation and PV Resolution per run submission tools.
The list of features introduced in this PR are:
submitPVValidationJobs.py
;PR validation:
Relies on the existing (and augmented) unit tests, both in the regular build
CMSSW_11_2_X_2020-10-01-2300
and in the Py3 buildCMSSW_11_2_PY3_X_2020-10-04-2300
.if this PR is a backport please specify the original PR and why you need to backport that PR:
This is not a backport, and no backport is immediately needed.