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
Fix for Legacy2016 Smearings cms-data/EgammaAnalysis-ElectronTools#6 … #4062
Fix for Legacy2016 Smearings cms-data/EgammaAnalysis-ElectronTools#6 … #4062
Conversation
A new Pull Request was created by @fabiocos (Fabio Cossutti) for branch IB/CMSSW_9_4_X/gcc630. @cmsbuild, @smuzaffar, @gudrutis, @mrodozov can you please review it and eventually sign? Thanks.
|
@smuzaffar @slava77 this should be tested on top of CMSSW_9_4_MAOD_X |
On 5/31/18 7:28 AM, Fabio Cossutti wrote:
@smuzaffar <https://github.com/smuzaffar> @slava77
<https://github.com/slava77> this should be tested on top of
CMSSW_9_4_MAOD_X
—
Is there a way to do it with cms-bot/jenkins?
|
not automatically via "please test" command but once job starts in jenkins then I can change the release format to be 9.4.maod.x |
please test @smuzaffar so please change the release directly in jenkins, thanks |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
these are in the expected places in the 2016 re-miniAOD workflow 136.7611 I expect that the MC part should behave the same as in the 10_2_X tests mentioned in |
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_9_4_X/gcc630 IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
@slava77 changes specific to MC are from PixelPhase1v DQM, that shows non reproducibility on 94X and looks to me unrelated to this PR |
+1 |
Backport of #4036