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
Improvements in DBOutputService transaction workflow #36387
Improvements in DBOutputService transaction workflow #36387
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36387/27169
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36387/27173
|
A new Pull Request was created by @ggovi for master. It involves the following packages:
@malbouis, @yuanchao, @cmsbuild, @ggovi, @francescobrivio, @tvami can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: UnitTests Unit TestsI found errors in the following unit tests: ---> test testCondToolsDQMUpload had ERRORS ---> test EcalADCToGeV_update_test had ERRORS ---> test EcalTPGBadStripStatus_O2O_test had ERRORS ---> test EcalIntercalibConstants_O2O_test had ERRORS and more ... Comparison SummarySummary:
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36387/27250
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-dc7587/21114/summary.html Comparison SummarySummary:
|
+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. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The PoolDBOutputService object is the main CMSSW interface for the creation of new condition set and the update of Tags in the central database. The actions supported ( create, append, write, erase, ... ) require to operate within a transactional workflow, generally explicit, optionally implicit. The overall model and the implementation has been revisited, simplifying and clarifying the usage of the interface on the client side.
PR validation:
unit tests and integration tests