-
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
convert mkfit output warnings to LogInfo #35802
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35802/26166
|
A new Pull Request was created by @slava77 (Slava Krutelyov) for master. It involves the following packages:
@jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b45b31/19864/summary.html Comparison SummarySummary:
|
This is a quite a significant reduction, but there are still quite a few warnings coming indirectly via |
at least the first warning comes after a propagation of the mkfit track output state to the last hit. So, this PR is as good as it gets at this point on the CMSSW side. |
Based on your comment #35802 (comment) I think so, though I'd like to understand if we should (could?) plan for an update of the mkFit external within the time of closure of 12_1_0 for further clean-up. |
I opened trackreco/mkFit#373 |
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 |
this is in a follow up to #35798
the rate of warnings about bad candidates in the MkFitOutputConverter is too large to handle in production logs.
This PR silences them for now.
136.874 log example