[hotfix][tests] Tolerate schema change timeout failure and retry, suppress false alarms#3676
Closed
yuxiqian wants to merge 1 commit into
Closed
[hotfix][tests] Tolerate schema change timeout failure and retry, suppress false alarms#3676yuxiqian wants to merge 1 commit into
yuxiqian wants to merge 1 commit into
Conversation
…press false alarms This doesn't solve the root problem at all. Just makes the CI not to fail due to the "FlushEventStuck" reason. tried to solve the real problem but failed. doesn't matter anyway. Signed-off-by: yuxiqian <34335406+yuxiqian@users.noreply.github.com>
Member
Author
|
Low priority but should improve CI passing rate, cc @ruanhang1993 |
Member
Author
|
After some pressure tests, it turns out that job just keeps stuck even after restarts. Seems some special pattern of event mixture will 100% cause FlushEvent to stuck. This won't make anything better, closing it. |
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
1 participant
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.
This doesn't fix the root cause of this failure at all. It just adjusts the testing configuration and allows job failover and restart the job when the "flush event stuck" problem occurs, instead of reporting CI failure immediately.