-
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
Fix try/catch in Vx3DHLTAnalyzer #39285
Fix try/catch in Vx3DHLTAnalyzer #39285
Conversation
type bug-fix |
test parameters:
|
was this tested against the problematic data leading to the crash online? |
I tried running it on the RAW data of the problematic run, but I observed no crash...I don't think we still have the streamer files for that run... As substitute I increased manually the VtxError parameter in order to make the same crash appear (FatalRootError: @sub=Minuit2) and it is catched correctly, but yes I agree it's not the same thing... |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39285/31947
|
A new Pull Request was created by @francescobrivio for master. It involves the following packages:
@malbouis, @pmandrik, @emanueleusai, @ahmad3213, @tvami, @cmsbuild, @jfernan2, @saumyaphor4252, @ggovi, @francescobrivio, @micsucmed, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
according to #38687 (comment) there are streamer files, or did I misunderstand? |
please see my answer to that post, the misunderstanding is from the DQM-DOC side 😄 |
ok I'm in contact with DQM-DOC (@vicha-w) to get hold of the needed streamer files. I will update you once I can run a test on them. |
@cmsbuild, please test
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6a15fe/27269/summary.html Comparison SummarySummary:
|
I tried running on LSs 1-2-3 of the problematic run ( The only way I have to mimic this error is to enlarge the Anyway this is a "bug-fix" because in the original try/catch I added the return codes were not correctly propagated...what do you think @mmusich? |
@francescobrivio |
does this test include the changes proposed in this PR? |
@mmusich |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39285/32039
|
Pull request #39285 was updated. @malbouis, @pmandrik, @emanueleusai, @ahmad3213, @tvami, @jfernan2, @saumyaphor4252, @ggovi, @francescobrivio, @micsucmed, @rvenditti can you please check and sign again. |
I agree with you, but I'd prefer to leave this to a future PR since it is addressing a different issue. |
It might be that the Minuit exception is linked to the vertices given in input, but sure let's deal with that later as this PR offers a safety net against crashes at P5. |
Good point!
Please see #39339 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6a15fe/27406/summary.html Comparison SummarySummary:
|
+db
|
+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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
and also: #39341 (comment) :D |
+1 |
PR description:
In #38687 a
try/catch
statement was added in the DQM clientVx3DHLTAnalyzer
to protect the client against Minuit2 FatalRootError, but the return codes were not set properly, as reported in #38687 (comment).This PR provides a bugfix.
PR validation:
Code compiles + run the unitTest.
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:
Not a backport.
Backports to 12_5_X and 12_4_X will be provided soon.
FYI @dinardo @mmusich