test(bigtable): disable testDeadlockPrevention to fix CI execution timeout - #13902
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request disables the testDeadlockPrevention test in ClientConfigurationManagerTest.java by adding the @disabled annotation. The reviewer suggests providing an explanation or tracking issue within the @disabled annotation as a best practice to ensure the test is eventually re-enabled.
lqiu96
force-pushed
the
fix/disable-bigtable-timeout-tests
branch
2 times, most recently
from
July 27, 2026 17:53
4244522 to
0303142
Compare
mutianf
approved these changes
Jul 27, 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
2 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.
Disable flaky test (#13903). Bigtable unit tests are run as part of the main units test suite. This is causing some of our required checks to timeout after ~360 minutes. Disable flaky tests to be re-enabled after they get resolved.