Skip to content

Conversation

@prathmeshcc
Copy link
Collaborator

@prathmeshcc prathmeshcc commented Dec 1, 2025

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.

@prathmeshcc prathmeshcc requested a review from a team as a code owner December 1, 2025 23:10
@product-auto-label product-auto-label bot added the api: spanner Issues related to the Spanner API. label Dec 1, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @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 chrono arithmetic. By updating the calculation for time intervals, such as ensuring an hour is precisely 3600 seconds, the change aims to eliminate flakiness and improve the accuracy of test results related to time-based operations.

Highlights

  • Chrono Arithmetic Correction: Updated chrono arithmetic in the Spanner Interval integration test to ensure precise time calculations, specifically for adding time intervals like an hour.
  • Test Flakiness Resolution: This change aims to resolve potential flakiness and inaccuracies in test results that were previously caused by incorrect time interval calculations.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@prathmeshcc prathmeshcc changed the title fix(spanner): correct chrono arithmetic in Interval integration test (#15163) fix(spanner): correct chrono arithmetic in Interval integration test Dec 1, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a 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.

@codecov
Copy link

codecov bot commented Dec 1, 2025

Codecov Report

❌ Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 92.94%. Comparing base (d0dc97e) to head (53521db).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...r/integration_tests/data_types_integration_test.cc 0.00% 4 Missing ⚠️
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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@mpeddada1
Copy link
Collaborator

/gemini review

@prathmeshcc prathmeshcc enabled auto-merge (squash) December 10, 2025 18:37
@prathmeshcc prathmeshcc merged commit c08a8b3 into googleapis:main Dec 10, 2025
65 of 70 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the Spanner API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants