-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Correction of a tag name (Ecal O2O unit test fix) #23610
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23610/5229 |
A new Pull Request was created by @depasse for master. It involves the following packages: CondTools/Ecal @ggovi, @cmsbuild 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:
|
Hypothesis : this code was created on 17 February. |
+1 |
This pull request is fully signed and it will be integrated in one of the next master 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) |
@depasse thank you for the explanation, it makes sense |
+1 |
Just a small comment to @depasse : Please when you make a PR, make an explicit title - It is not possible to understand from this title if the tag you are changing is an hcal, strips, beamspot , or ecal tag ... The titles of PRs are very important, thank you . |
@boudoul you are right, this title was bit too generic... I have appended a note |
Thank you @fabiocos ! |
Realted to the error described in PR #23606