-
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
Fixing bug in HLTriggerJSONMonitoring L1 and prescale module idenfication : 12_5_X #39811
Fixing bug in HLTriggerJSONMonitoring L1 and prescale module idenfication : 12_5_X #39811
Conversation
A new Pull Request was created by @Sam-Harper (Sam Harper) for CMSSW_12_5_X. It involves the following packages:
@cmsbuild, @missirol, @Martin-Grunewald can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
backport of #39779 |
type bugfix |
-1 Failed Tests: RelVals-INPUT RelVals-INPUT
Comparison SummarySummary:
|
+hlt
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_5_X IBs (but tests are reportedly failing) and once validation in the development release cycle CMSSW_12_6_X is complete. 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 |
merge |
PR description:
HLTriggerJSONMonitoring is how the HLT reports path rates to OMS. It was updated in Jun (#38418) to better support DatasetPaths.
In doing so a bug was introduced in that if a path is after a dataset path, the wrong L1 and prescale module will be identified.
Additionally the logic was improved to only consider the first seed module and also to disregard ignored modules. This fixes problems in some paths which have additional L1 seed modules which are ignored as they want to use this data later in the path.
Credit goes to Adelina Lintuluoto (@alintulu) for spotting this issue in the hilton tests.
PR validation:
validation in : #39779
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
backport of #39779 as its needed to fix a bug in monitoring at P5