Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@abhizer
Copy link
Contributor

@abhizer abhizer commented Jan 30, 2026

In sync tests, wait until the most recently checkpoint, the one with all the data is synced.
This didn't show up previously, as all the data was inserted and executed within the checkpoint interval of 5s, and this checkpoint was synced within the sync interval of 10s.

Copilot AI review requested due to automatic review settings January 30, 2026 10:06
In sync tests, wait until the most recently checkpoint, the one with all
the data is synced.
This didn't show up previously, as all the data was inserted and
executed within the checkpoint interval of 5s, and this checkpoint was
synced within the interval of 10s.

Signed-off-by: Abhinav Gyawali <[email protected]>
@abhizer abhizer force-pushed the py-fix-flaky-sync-test branch from 6a3251f to 4b6be5a Compare January 30, 2026 10:07
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adjusts the checkpoint sync test to wait for the most recent checkpoint (containing all data) to be synced, reducing flakiness in automated sync scenarios.

Changes:

  • Import UUID and use it to compare checkpoint identifiers to ensure the synced checkpoint is at least as recent as the created checkpoint.
  • Add additional logging of checkpoint UUIDs for easier debugging.
  • Introduce a brief delay and new assertions in both automatic and manual sync paths to ensure the expected checkpoint has been synced.

@abhizer abhizer added this pull request to the merge queue Jan 30, 2026
Merged via the queue into main with commit 6e8fbd8 Jan 30, 2026
1 check passed
@abhizer abhizer deleted the py-fix-flaky-sync-test branch January 30, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants