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
Remove --harvesting AtJobEnd option in GEN Relval workflows #25339
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25339/7362 |
A new Pull Request was created by @SanghyunKo (Sanghyun Ko) for master. It involves the following packages: Configuration/PyReleaseValidation @pgunnell, @zhenhu, @prebello, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+1 |
merge GEN workflows correctly produce DQM output in standalone test runs producing as output |
In recent 10_4_0_pre2 release validation campaign, DQMIO files of ALL GEN Relval samples were not uploaded to DQM server due to the wrong run number (999999). This was caused by PR #24920 , the dummy run number parameter of all GEN workflows was affected by the change introduced in DQMSaverAtJobEnd_cff.py because all GEN Relval workflows were using '--harvesting AtJobEnd' option. Since there is no point of using '--harvesting AtJobEnd' option (there is only single harvesting job like any other Relval workflows), simply removing this option can fix the issue.
Fix the issue #25272 . See JIRA ticket 4020 for detailed discussions.