[Test] Fix flaky heartbeat executor bound test - #18773
Merged
jt2594838 merged 1 commit intoSep 30, 2026
Merged
Conversation
jt2594838
approved these changes
Sep 30, 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.
Description
testHeartbeatExecutorIsBoundedassumed the shared heartbeat executor had its full capacity available to the test. Concurrent heartbeat tasks can consume a slot, causingsubmitProviderHeartbeatto returnnullbefore the test finishes filling the executor. The cleanup loop then dereferences thatnullfuture.Submit blocking tasks until the executor rejects one, retain only accepted futures, and verify rejection occurs within the configured thread and queue capacity.
Tests
mvn spotless:apply -pl iotdb-client/subscriptionmvn -pl iotdb-client/subscription -Dtest=SubscriptionConsumerHeartbeatIsolationTest test