-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Convert all remaining MessageLogger configurations to new syntax #32244
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
Conversation
|
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32244/19999
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
fa56b51 to
db0e790
Compare
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32244/20000
|
|
+1 |
|
@Dr15Jones but it seems ie, it was removed, and What should we use as replacement to get the above messages? |
Yes, that will allow INFO messages to be seen as the default is still to have a threshold of INFO but with the default For reference, the how to on the new syntax can be found here |
|
Hmm, still a problem: where the offending lines around 92189 are: ?? |
|
@Martin-Grunewald I believe the problem is you do not start from the process.MessageLogger.TriggerSummaryProducerAOD=cms.untracked.PSet()which explicitly set the type. |
|
@Martin-Grunewald out of curiousity, what do you get if you do process.MessageLogger.dumpPython()? |
|
No output... |
|
|
but I had to comment out the offending assignments. |
|
And when I put them back with |
|
@Martin-Grunewald as I suspected, the various |
|
@Martin-Grunewald do you know where cout = cms.untracked.PSet(
placeholder = cms.untracked.bool(True)
),comes from in your configuration? |
|
ConfDB keeps nested parameters (ie parameters inside PSets) and adds/removes top level parameters (only), but at the same time we can add/remove those by hand. |
|
The easiest would be just to remove the whole |
|
This is a top level parameter so ConfDB foces it to exist when seeing it in |
|
But the settings for |
|
So I am presently running from master, and I get [root@25fa425c5ca5 CMSSW_11_2_0_pre8]# python
Python 2.7.15+ (default, May 7 2020, 19:47:02)
[GCC 8.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from FWCore.MessageService.MessageLogger_cfi import MessageLogger
>>> print(MessageLogger.cout.dumpPython())
cms.untracked.PSet(
enable = cms.untracked.bool(False),
enableStatistics = cms.untracked.bool(False),
lineLength = cms.optional.untracked.int32,
noLineBreaks = cms.optional.untracked.bool,
noTimeStamps = cms.optional.untracked.bool,
resetStatistics = cms.untracked.bool(False),
statisticsThreshold = cms.optional.untracked.string,
threshold = cms.optional.untracked.string,
allowAnyLabel_=cms.optional.untracked.PSetTemplate(
limit = cms.optional.untracked.int32,
reportEvery = cms.untracked.int32(1),
timespan = cms.optional.untracked.int32
)
)
>>> |
|
That's what I mean: cout is a top level parameter, so ConfDB parsing keeps it as it sees it during parsing of the MessageLogger cfi. |
|
Hmm, for some reason ConfDB parsing keeps both cout and cerr... |
|
NOTE: in my dump I just dumped |
|
Ah, ok. |
|
The next error is: I do not understand why these parameters which are in the cfi now cause an error! |
|
Looks like the above are caused by the nested incarnations (inside cerr), so I can remove them. But then I get an error in Please advise. |
|
It seems I can get rid of |
I'm abit puzzled because there should not be any "top level Written that, does #32537 mean that you succeeded in migrating the MessageLogger configuration in ConfDB to the "new syntax"? |
|
Yes indeed. It must be some ConfDB idiosyncrasy, maybe because it is an untracked parameter. (It may be that in the distant past this untracked parameter was added by hand/hardwired in ConfDB's template for MessageLogger, which is/was a brittle feature we no longer use) |
PR description:
PR validation: