-
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 for conddb command line tool #34192
Fix for conddb command line tool #34192
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34192/23410
|
A new Pull Request was created by @ggovi for master. It involves the following packages: CondCore/Utilities @ggovi, @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
test parameters:
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fb8a28/16131/summary.html Comparison SummarySummary:
|
kindly ping @cms-sw/db-l2 |
+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 |
We provide a fix for the conddb tool:
conddb copy --toRun
When the input IOV set starts with timestamp = 0 or timestamp =1 ( both corresponding to 1970-01-01 00:00:00 ) a run matching for the conversion can't be found. This boundary condition is now identified , and an error returned.
Testing: local integration test