-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coverage: adjust threshold on source/server to fix flaky failure #15238
Conversation
The coverage recently has been flaky between 94.4 and 95.1. What's worse is this is somehow deterministic, i.e. on some pull requests, retesting would not work to go green. Signed-off-by: Takeshi Yoneda <[email protected]>
+1 #15117 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically LGTM: I think it's something we need to fix but the flakiness of this coverage issue should not be a tax on all unrelated PRs.
But can you add an Issue describing what you've learned about the flake, and reference it here from this comment, so we are not tempted to "tighten" the coverage requirements again and re-introduce flakes?
Agreed. I'm on it. |
#15239 created the tracker. |
Signed-off-by: Takeshi Yoneda <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix + issue and sorry for the noise
The coverage on source/server recently has been flaky between 94.4 and 95.1. What's worse is
this is somehow deterministic, i.e. on some commits, retesting would not work to go green.
I have encountered this several times in a last few weeks, for example, #15210 this is clearly unrelated to this coverage issue. You can see the same flake is happening to other PRs.
I see that the root cause sits in
source/server/connection_handler_impl.cc
, but I would like to introduce this change as a temporary workaround.Signed-off-by: Takeshi Yoneda [email protected]