-
Notifications
You must be signed in to change notification settings - Fork 432
fix(spanner): correct chrono arithmetic in Interval integration test #15810
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(spanner): correct chrono arithmetic in Interval integration test #15810
Conversation
Summary of ChangesHello @prathmeshcc, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an issue in the Spanner Interval integration test where time additions were not using correct Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request correctly identifies an area for improvement in an integration test by replacing a magic number for time duration with std::chrono arithmetic. However, the implementation introduces a new potential for test flakiness by making two separate calls to std::chrono::system_clock::now(). My review includes a suggestion to refactor this to use a single time point, which will make the test more reliable and the code cleaner.
google/cloud/spanner/integration_tests/data_types_integration_test.cc
Outdated
Show resolved
Hide resolved
9882651 to
a5c6906
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15810 +/- ##
==========================================
- Coverage 92.95% 92.94% -0.02%
==========================================
Files 2458 2458
Lines 227589 227588 -1
==========================================
- Hits 211561 211537 -24
- Misses 16028 16051 +23 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
google/cloud/spanner/integration_tests/data_types_integration_test.cc
Outdated
Show resolved
Hide resolved
a5c6906 to
85a6816
Compare
|
/gemini review |
The integration test for Spanner Intervals previously used non chrono literal logic
for time additions. This commit updates the chrono arithmetic to ensure hermetic logic and uses chrono literals.