RATIS-1491. TestNettyDataStreamChainTopologyWithGrpcCluster timed out after 100 seconds#583
Merged
szetszwo merged 3 commits intoapache:masterfrom Jan 18, 2022
Merged
Conversation
szetszwo
approved these changes
Jan 18, 2022
Contributor
szetszwo
left a comment
There was a problem hiding this comment.
+1 the change looks good.
Contributor
Author
|
Thanks @szetszwo for reviewing and committing it. |
symious
pushed a commit
to symious/ratis
that referenced
this pull request
Feb 28, 2024
… after 100 seconds (apache#583)
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
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.
What changes were proposed in this pull request?
Fix timeout in
DataStreamAsyncClusterTests.testMultipleStreamsMultipleServersStepDownLeaderhas 300 seconds timeout, but is frequently stopped after 100 seconds:Timeout specified in
@Test(timeout = ...)is limited by theBaseTest#globalTimeoutrule, which defaults to 100 seconds. We need to overridegetGlobalTimeout()to increase the rule's timeout.Remove ineffective timeout from
OutputStreamBaseTest.OutputStreamBaseTestalso has a test case which intends to increase timeout to 300 seconds. But this test case normally runs in less than 30 seconds:and intermittently times out even with 300 seconds (after applying the fix described above for
OutputStreamBaseTests):So I think we should apply the default 100 seconds timeout to save time in the failure case, and fix the test instead (filed RATIS-1493 for this).
https://issues.apache.org/jira/browse/RATIS-1491
How was this patch tested?
https://github.com/adoroszlai/incubator-ratis/runs/4849875094
https://github.com/adoroszlai/incubator-ratis/runs/4854999261