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
Fix the TriggerResultsFilter default configuration to skip the current process #35131
Fix the TriggerResultsFilter default configuration to skip the current process #35131
Conversation
please test |
type bugfix |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35131/25037
|
A new Pull Request was created by @fwyzard (Andrea Bocci) for master. It involves the following packages:
@Martin-Grunewald 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-35131/25049
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b11db7/18278/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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The default configuration of
TriggerResultsFilter
tries to read theTriggerResults
without specifying any process label, which is understood as wanting to read from the current process.This leads to test for the
TriggerResultsFilter
failing because of a conflict in the schedule.This PR updates the default configuration to ignore the current process.
PR validation:
HLTrigger/HLTfilters/test/triggerResultsFilter.py
now works: