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
Make DQMRootOutputModule to depend on all DQM modules via DQMTokens #29586
Conversation
The framework needs to be aware of the dependence.
The code-checks are being triggered in jenkins. |
FYI @schneiml |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29586/14911
|
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages: DQMServices/FwkIO @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @jfernan2, @fioriNTU can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
@makortel uh, so I was wrong? Thanks a lot, anyways! |
PR description:
#29553 implies that all data dependencies for modules in Tasks must be specified to keep those modules alive and running (in principle the proper dependencies should be declared anyway, that PR makes it necessary also in practice). It turned out that the
DQMRootOutputModule
currently does not declare dependencies on all the DQM analyzers. Easiest fix is to doconsumesMany<DQMToken, ...>
for both Lumi and Run products.Actually I tried first to use the
outputCommands
(which by the for some reason iscmssw/Configuration/EventContent/python/EventContent_cff.py
Lines 356 to 357 in 3f89112
which to me doesn't seem to make much sense), but that would require making
DQMToken
persistable, which would require an underscore a forbidden character for all modules producingDQMToken
. An underscore appears to be in wide use for DQM modules, which is why I scrapped that approach (I did some amount of migration to no-underscore module labels, if DQM is interested I can make pull request(s) of what I did).PR validation:
Limited matrix runs.