-
Notifications
You must be signed in to change notification settings - Fork 4.4k
introduce @phase2FakeHLT
and @phase2ValidationFakeHLT
DQM / Validation sequences
#47401
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
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47401/43784
|
@cmsbuild, please test |
+1 Size: This PR adds an extra 92KB to repository Comparison SummarySummary:
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@AdrianoDee, @Moanwar, @antoniovagnerini, @civanch, @DickyChant, @kpedro88, @mdhildreth, @miquork, @rseidita, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 |
+Upgrade |
@cms-sw/pdmv-l2 @cms-sw/dqm-l2 kind ping. |
+dqm
|
@cms-sw/pdmv-l2 another kind ping |
+pdmv
|
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. @rappoccio, @antoniovilela, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
There are still few phase-2 geometries in release for which we don't run the HLT step. Thus the HLT DQM and validation sequences (and harvestings) get run without purpose. This lead e.g. to the issue described at #47352 (comment) in which wf 24034.0 (that runs the
@fake2
menu) was trying to consume HLT collections that were not present on file.This PR introduces a
@phase2FakeHLT
(DQM) and a@phase2ValidationFakeHLT
(Validation) sequence that can be run in phase-2 workflows in which there is no intention to run the HLT step (similarly as for what is done in Run3).PR validation:
runTheMatrix.py -l phase2
runs finerunTheMatrix.py -l 24034.0 -t 4 -j 8 --ibeos
runs fine (this is for a geometry in which we don't run )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:
N/A