-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Validation fixes - 10_6_X #27224
Validation fixes - 10_6_X #27224
Conversation
type bug-fix |
A new Pull Request was created by @perrotta for CMSSW_10_6_X. It involves the following packages: Validation/EventGenerator @andrius-k, @kmaeshima, @schneiml, @efeyazgan, @cmsbuild, @jfernan2, @agrohsje, @fioriNTU, @alberto-sanchez, @qliphy can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
backport of #27116 |
+1 |
@jfernan2 apparently the comment must be in a separate line, otherwise the bot does not correctly set the status (it does not matter in this case, I take your signature) @efeyazgan @qliphy @alberto-sanchez I imagine this would be useful for GEN validation during UL activities |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_0_X is complete. 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) |
+1 |
PR description:
Backport of the fixes merged in master with #27116 for the UL release
Starting from some issue reported by the static analyzer, I think there are two real bugs in these Validation files which are fixed here:
A few other minor adjustments are also included here.
Furthermore, in order to recycle and cherry-pick the same commits as in the master version, the very first commit in this PR applies clang-format to the files affected, as it was done already in the master version.
Changes are expected in the DQM output because of the fixes (the same as in the mother version of this PR)
PR validation:
It compiles
if this PR is a backport please specify the original PR:
backport of #27116