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
Technical fixes to L1T code from 24242 #24274
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24274/5996 |
A new Pull Request was created by @fabiocos (Fabio Cossutti) for master. It involves the following packages: L1Trigger/L1TCalorimeter @nsmith-, @rekovic, @cmsbuild, @thomreis can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Thanks @fabiocos. I saw this just now as I am with limited access. +1 |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. 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) |
@davidlange6 I guess that at present we have no other way to detect python print statements not migrated to the new syntax than by visual inspection, am I correct? |
Right. There is an open issue against that.
… On Aug 13, 2018, at 4:02 PM, Fabio Cossutti ***@***.***> wrote:
@davidlange6 I guess that at present we have no other way to detect python print statements not migrated to the new syntax than by visual inspection, am I correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
The integration of #24242 has caused a couple of issues:
This PR addresses both issues, corresponding fixes should be backported to the version for 10_2_X.