-
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
New Run-3 MC GTs containing new pixel bad components #34450
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34450/23885
|
A new Pull Request was created by @tvami (Tamas Vami) for master. It involves the following packages:
@malbouis, @yuanchao, @cmsbuild, @tlampen, @pohsun, @francescobrivio, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b4fe37/16726/summary.html Comparison SummarySummary:
|
test parameters:
|
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b4fe37/16734/summary.html Comparison SummarySummary:
|
@qliphy @silviodonato @perrotta we see a lot of failures in |
seems related to #34445 |
Not all of these diffs come from DQM/TimingService though |
certainly all of the ones about
|
That's correct: some of them come from the new pixel bad components that we changed in the GTs, but it's a bit hard to exactly debug them among all the DQM TimerSevices failures. |
just to understand, will this PR be stalled until #34445 is solved? |
(just repeating what Francesco said) |
test parameters:
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b4fe37/16763/summary.html Comparison SummarySummary:
|
+alca
|
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, @perrotta (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Tracker DPG has an updated list of bad components for the Run-3 MCs. These GTs differ from the current autoCond GTs only in the tags requested in the HN message of [1] and presentation at the AlCaDB meeting [2], see also the diffs [3-5]
[1] https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/4423.html
[2] https://indico.cern.ch/event/1056952/#5-run3-pixel-bad-components-fo
[3] 2021: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/120X_mcRun3_2021_realistic_v2/120X_mcRun3_2021_realistic_v3
[4] 2023: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/120X_mcRun3_2023_realistic_v2/120X_mcRun3_2023_realistic_v3
[5] 2024: https://cms-conddb.cern.ch/cmsDbBrowser/diff/Prod/gts/120X_mcRun3_2024_realistic_v2/120X_mcRun3_2024_realistic_v3
PR validation:
runTheMatrix.py -l limited,11634.0,12434.0,12834.0 --ibeos -j8
tests pass
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 backport is not needed