-
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 GlobalAlgBlkUnpacker to throw error in the case of headers received in the wrong order #41401
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41401/35266
|
A new Pull Request was created by @aloeliger (Andrew Loeliger) for master. It involves the following packages:
@epalencia, @cmsbuild, @cecilecaillol, @aloeliger can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
EventFilter/L1TRawToDigi/plugins/implementations_stage2/GlobalAlgBlkUnpacker.cc
Outdated
Show resolved
Hide resolved
please abort |
…eived in the wrong order
c035d0c
to
f93445c
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41401/35267
|
Pull request #41401 was updated. @epalencia, @cmsbuild, @cecilecaillol, @aloeliger can you please check and sign again. |
please test |
Hi Andrew, this looks good to me! One thing I noticed during debugging is that https://github.com/cms-sw/cmssw/blob/CMSSW_13_0_3/EventFilter/L1TRawToDigi/plugins/L1TRawToDigi.cc#L269-L276 are Cheers, |
@dinyar In principle I would agree, but that is probably not for this PR. I also noticed that there are some TODO statements there about handling the error. I don't know how one would handle that, but @bundocka is actually listed as the author of that particular block, so perhaps we can ask him to clarify if that should be changed to an exception, or if there was ever planned error handling of that section that simply never got implemented. |
I know too little about the L1T unpackers to judge this, but I agree those likely need to be changed to at least
I agree with this, too. The reason is that it would be useful to have the backport included in the next 13_0_X release, which means getting #41402 integrated asap. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c28387/32129/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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR has been opened in response to L1 JIRA ticket 411. HLT has noticed problems regarding the L1TRawToDigi process, which has been tracked to an issue in the GlobalAlgBlk unpacker receiving blocks and header IDs out of order. This causes a bad access/
->at
call,of a following BXVector, which fails somewhat un-informatively. This PR has been opened to produce a more informative failure message in case the initial header ID assumption fails.@dinyar @kbunkow @missirol @alintulu I figured you would like to be kept in the loop on this.
PR validation:
All code compiles, has had code-formatting applied, and passes code checks. When testing on error events from the open JIRA ticket, the cms::exception reports instead of bad vector access errors.
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:
This PR is not a backport, however a backport may be expected for CMSSW_13_0.