-
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
update testTriggerEventAnalyzers
unit test (new input, more events)
#42415
update testTriggerEventAnalyzers
unit test (new input, more events)
#42415
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42415/36425
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. 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 for CMSSW_13_3_ASAN_X |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d36d32/33965/summary.html |
-1 Failed Tests: RelVals-INPUT RelVals-INPUTThe relvals timed out after 4 hours. Comparison SummarySummary:
|
+hlt
|
This pull request is fully signed and it will be integrated in one of the next master IBs (but tests are reportedly failing). 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:
This PR changes the input file of the unit test
testTriggerEventAnalyzers
. A ttbar-MC file is used (like before #41350) to exercise more triggers compared to the current input file. The new input file was made with an HLT menu which includes the fix discussed in #41045 (see also CMSHLT-2750). The number of events used in this unit test is also increased without increasing significantly the duration of the test (a few seconds).PR validation:
The unit test
testTriggerEventAnalyzers
passes in an ASAN IB.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