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
Logging service for Condition Workflows #31667
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31667/18787
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
Wondering how to avoid to fix this type of issues AFTER the PR submission. Running scram build code-format before the first submission seems to be not the way... |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31667/18788
|
A new Pull Request was created by @ggovi for master. It involves the following packages: CondCore/CondDB @yuanchao, @christopheralanwest, @tocheng, @cmsbuild, @tlampen, @ggovi, @pohsun can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins.
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31667/18974
|
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
+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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
We are adding a new service to provide recollection of log messages, with the aim to store them in the database, related to the condition data stored in the same context.
The target and main use case for this implementation are the workflows providing the lumi-based conditions for HLT.
PR validation:
A dedicate unit tests validates the base Logger. Two integration tests are exercising the use case with an Oracle db destination.