-
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
Removal of ZDC LUT file in caloParamsHelper and L1T workflow #43502
Conversation
Removal of zdc LUT file query from L1TCaloStage2ParamsESProducer - obsolete Also need to mod the caloParams file
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43502/38078
|
A new Pull Request was created by @cfmcginn (Chris) for master. It involves the following packages:
@epalencia, @cmsbuild, @aloeliger can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43502/38346
|
Pull request #43502 was updated. @cmsbuild, @aloeliger, @epalencia can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7f8583/36803/summary.html Comparison SummarySummary:
|
+l1 |
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. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Removal of zdc LUT file query from L1TCaloStage2ParamsESProducer - obsolete
Also need to mod the caloParams file
PR description:
This PR removes ZDC LUT in CaloParamsHelper, made obsolete by recent PR:
#42818
PR validation:
With PR, pre-existing L1Trigger development workflows no longer require presence of an unused and obsolete LUT
scram b runtests has some seemingly unrelated failures, but the most relevant test, L1Trigger/L1TGlobal/testL1TGlobalProducer, passes
Both of the below are applied
scram build code-checks
scram build code-format
Unclear if backport is necessary at this time; @bundocka can comment - given the small size of the PR, should be quick to prepare