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
Prevent pLHE workflows to start from input files #27285
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27285/10492
|
A new Pull Request was created by @fabiocos (Fabio Cossutti) 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 workflow 1370.0,25215.0 |
The tests are being triggered in jenkins. |
please abort |
Jenkins tests are aborted. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27285/10494
|
please test workflow 1370.0,1370.17,1370.18,25215.0,25215.17,25215.18 |
The tests are being triggered in jenkins. |
Comparison job queued. |
obviously much faster... |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
@prebello @zhenhu @kpedro88 I take the previous signature as valid, the only change is the number of events processed in the LHE and GEN,SIM steps (irrelevant for the final DQM result, but important for the performance impact on the tests). Please check and sign or comment otherwise, I want to give this PR a try in next IB, before the big Sunday rebuild |
+1 |
merge |
+1 |
PR description:
PR #26875 has added 6 new test workflows based on pLHE input to GEN-SIM. Although the basic workflows run smoothly, when the
-i all
is used for runTheMatrix.py in IB , 1370.0,1370.17 and 1370.18 fail due to the fact that the generator part is split in two, and the standard logic of PyReleaseValidation fail, see issue #27248. A simple workaround is to force these workflows to be always fully executed, regardless of the input option (to be verified the possible impact on resources).PR validation:
All the pLHE workflows have been verified to pass the first two steps both with and without the
-i all
option of runTheMatrix.py.