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
move *egmGsfElectronIDsForDQM module to a cms.Task #21468
Conversation
Avoid causing an unrunnable module schedule by moving egmGsfElectronIDsForDQM and B2GegmGsfElectronIDsForDQM to be on a cms.Task which is associated with the cms.Sequence which previously held the module.
The code-checks are being triggered in jenkins. |
+code-checks |
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @Dr15Jones (Chris Jones) for master. It involves the following packages: DQMOffline/Trigger @vazzolini, @kmaeshima, @dmitrijus, @cmsbuild, @jfernan2, @vanbesien can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready There are some workflows for which there are errors in the baseline: Comparison Summary:
|
merge |
Avoid causing an unrunnable module schedule by moving egmGsfElectronIDsForDQM
and B2GegmGsfElectronIDsForDQM to be on a cms.Task which is associated
with the cms.Sequence which previously held the module.
This fixes the release validation failure in the IBs for workflow 136.7802.