-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Phase2-hgx360M Change 2026 to Run4 in the scenario definitions of the scripts in Validation/Geometry #46680
Conversation
cms-bot internal usage |
@cmsbuild Please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46680/42608 |
A new Pull Request was created by @bsunanda for master. It involves the following packages:
@Dr15Jones, @antoniovagnerini, @bsunanda, @civanch, @kpedro88, @makortel, @mdhildreth, @rseidita can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Expand to see more relval errors ...
Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
@cmsbuild Please test |
-1 Failed Tests: UnitTests RelVals Unit TestsI found 1 errors in the following unit tests: ---> test TestDQMGUIUpload had ERRORS RelVals
|
@cmsbuild Please test |
-1 Failed Tests: UnitTests Unit TestsI found 1 errors in the following unit tests: ---> test TestDQMGUIUpload had ERRORS Comparison SummarySummary:
|
@cmsbuild Please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-46680/42639 |
Pull request #46680 was updated. @Dr15Jones, @antoniovagnerini, @bsunanda, @civanch, @kpedro88, @makortel, @mdhildreth, @rseidita can you please check and sign again. |
@cmsbuild Please test |
+1 Size: This PR adds an extra 16KB to repository Comparison SummarySummary:
|
+geometry |
+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. @antoniovilela, @rappoccio, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Change 2026 to Run4 in the scenario definitions of the scripts in Validation/Geometry
PR validation:
Tested all the scripts
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Nothing special