[Improve][Connector-V2][Jdbc] Increase timeout for schema change IT to fix flaky test#10258
Merged
corgy-w merged 2 commits intoJan 4, 2026
Merged
Conversation
…o fix flaky test - Increase initial data sync timeout from 30s to 60s - Increase add_columns schema change timeout from 30s to 60s - Increase main data assertion timeout from 60s to 120s - Increase additional assertion timeout from 30s to 60s This fixes intermittent CI failures in SqlServerSchemaChangeIT and PostgresSchemaChangeIT caused by insufficient timeout in slower CI environments.
dybyte
reviewed
Dec 30, 2025
… change integration tests
dybyte
approved these changes
Dec 30, 2025
chl-wxp
approved these changes
Dec 31, 2025
corgy-w
approved these changes
Jan 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of this pull request
This fixes intermittent CI failures in SqlServerSchemaChangeIT and PostgresSchemaChangeIT caused by insufficient timeout in slower CI environments.
Does this PR introduce any user-facing change?
How was this patch tested?
Check list
New License Guide
incompatible-changes.mdto describe the incompatibility caused by this PR.