-
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
Add preliminary GTs for 2023 MC #41947
Add preliminary GTs for 2023 MC #41947
Conversation
urgent
|
@cmsbuild please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41947/35919
|
A new Pull Request was created by @francescobrivio for master. It involves the following packages:
@tvami, @saumyaphor4252, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@francescobrivio , I think we also need to update
@cms-sw/l1-l2 @eyigitba @caruta , there are L1T-related errors in the addOnTests, see
|
-1 Failed Tests: RelVals RelVals-INPUT AddOn RelVals
RelVals-INPUT
AddOn Tests
|
Ciao @missirol, but that is for data right? here i'm only touching MC GTs. We will update the data GTs in a separate PR if that's ok for you?
I have just re run |
Okay. It can be done in a separate PR (plus backports), but I would just find it easier to be consistent and, in one go, update the L1T menu in all wfs that use a Run-3 HLT menu (the only reason it works now is that the new L1T menu happens to be compatible with the current Run-3 HLT menu). The update of the L1T menu in the other wfs [*] would have to come soon (next few days), before we introduce the next HLT menu, because we know the latter will only be compatible with the latest L1T menu (i.e. "L1T-v1_2_0"). [*] By the way, this also applies to the 2024 MC GT, since we use the Run-3 HLT menu in those wfs. |
then I would rather descope all the L1T+HLT related updates in a separate PR (data and MC alike), unless they critically depend on some of the other subdetector conditions. |
Ah, this is my bad actually. I should have modified this |
@eyigitba for my understanding: how is this goign to be fixed? Do you need a PR or a new tag? Because ideally this tag should be used in 13_0_X and 13_1_X and for the 2023 MC production...so if a new PR (and release) is needed, then it should be done ASAP! |
Hi @francescobrivio , this will require a PR to be consistent. Technically we can do it by customizing a tag for just MC production, but I'm not sure if this is the best idea. If you want we can discuss this over zoom to understand which solution would be better. |
Ok I discussed with Efe and we are testing a fix for this locally. |
test parameters: |
@cmsbuild please test |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummarySummary:
|
I think we can ignore this:
while this:
is expected I'd say, given that we have changed 54 tags in the 2023 MC realistic GT! |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-89f8dd/33164/summary.html Comparison SummarySummary:
|
+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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1
|
PR description:
This PR updates the GTs for the 2023 MC production to preliminary GTs, as detailed in this CMSTalk post.
Important Note:
These GTs do not yet contain all the conditions needed for the 2023 MC production as a few of them are still work in progress, but, since most of them are already available, we decided to start adding them to the release so they can be validated via the usual release validation.
GT differences:
PR validation:
Successfully run:
Backport:
Not a backport.
Backports to 13_1_X and 13_0_X will be opened only after all the conditions are available.