-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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 the data type being passed to writeOneIOV in WritePPSAssociationCuts.cc #36291
Fix the data type being passed to writeOneIOV in WritePPSAssociationCuts.cc #36291
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36291/26994
|
A new Pull Request was created by @wpcarvalho (Wagner Carvalho) for master. It involves the following packages:
@cmsbuild, @ggovi, @tvami, @malbouis, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
type bug-fix |
@cmsbuild , please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-156528/20845/summary.html Comparison SummarySummary:
|
+db
|
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 |
Hi Francesco. Thanks for pointing it out!
|
PR description:
This is a simple PR to correct the data type being passed to
poolDbService->writeOneIOV
in the moduleWritePPSAssociationCuts.cc
.As it currently is, the object stored in the database is of type
PPSAssociationCutsconst*
. The proposed fix allows to correctly save a object of typePPSAssociationCuts
.@fabferro @clemencia @sgrzegorz @jan-kaspar @grzanka
PR validation:
Local tests writing and retrieving data to a sqlite file using the tools in
CondTools/CTPPS
:CondTools/CTPPS/test/write_PPSAssociationCuts_cfg.py
CondTools/CTPPS/test/retrieve_PPSAssociationCuts_cfg.py
After the fix, I was able to correctly retrieve the conditions data.
if this PR is a backport please specify the original PR and why you need to backport that PR:
Not a backport.
Before submitting your pull requests, make sure you followed this checklist: