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
DQM: fix some autoDQM.py harvesting sequences #29343
Conversation
It is used in various places to indicate that no modules should be loaded.
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-29343/14432
|
A new Pull Request was created by @schneiml (Marcel Schneider) for master. It involves the following packages: Configuration/Applications @andrius-k, @kmaeshima, @schneiml, @cmsbuild, @silviodonato, @franzoni, @jfernan2, @fioriNTU, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test This has some chance of blowing up due to more undefined harvesting sequences. Let's see. |
The tests are being triggered in jenkins. |
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 looks good so far, though be aware of potential failures due to misconfigured harvesting in the IB tests. |
+operations |
+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 be automatically merged. |
@schneiml we are getting errors in CMSSW_11_1_X_2020-04-02-1100 in wf 140.0, 145.0, 150.0 . Do you think it is related to this PR? Tomorrow I will check it better. |
@silviodonato yep, that is related. |
Do you mean we have to remove |
|
#29393 should fix the error |
PR description:
It turns out that
ConfigBuilder
treats failing to find a HARVESTING sequence not as an error, and in fact we have some non-existing sequences inautoDQM.py
. One of them isDQMHarvestDCS
, which I forgot to remove in #28829.But also
DQMNone
, which is used to signify that there is nothing to do (''
could be understood as default sequence, as usual incmsDriver
) is not actually defined in harvesting. So I added that to all the main config files.Finally, this PR makes
ConfigBuilder
fail on undefined harvesting sequences, like it does for other sequences.PR validation:
Functionality should not be affected, but misconfigured jobs may crash now. I expect some PR and even IB failures untilwe catch all of them.