opened
makortel
username_0
#### 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 do `consumesMany<DQMToken, ...>` for both Lumi and Run products.

Actually I tried first to use the `outputCommands` (which by the for some reason is
https://github.com/cms-sw/cmssw/blob/3f89112fddb9bd4f384fa7acacc5fb81720bee16/Configuration/EventContent/python/EventContent_cff.py#L356-L357
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 producing `DQMToken`. 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.
Make DQMRootOutputModule to depend on all DQM modules via DQMTokens
issue
created
makortel
username_0
FYI @username_3
comment
created
makortel
username_0
@cmsbuild, please test
comment
created
jfernan2
username_1
+1
comment
created
silviodonato
username_2
+1
comment
created
schneiml
username_3
@username_0 uh, so I was wrong?

Thanks a lot, anyways!
comment