-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
FLAKE: TestKVDelete #14275
Comments
Just took a brief look, even on my more powerful box that test takes nearly 12s and comes very close to the defined timeout after adding a print for the time left:
Shall we increase the timeout for those tests? Alternatively there could also be two timeouts, one for spawning the cluster (5s?) and another for the test execution.
This message happens 695 times in the log so it's probably not related to that test flaking, but still interesting that it happens so frequently. |
Hmm, that's weird, I would look into why this test took so long. Possibly look into how much it took when the test was introduced. |
Good point, the test from #13753 takes only 3s instead of 12s. I'm going to bisect the changes since then and see what made it so much longer. |
The last one that takes 3s was in e4d34f21bc92b6e4c3255a9c893a2afea07a05e0 The runtime then doubled starting with #13864 and commit 63346bfead7dd9ad071485d7cc7d6c8bd9fc36b7 or more probably: e5bf230 I'll check deeper tomorrow which of the changes in there causes this. |
I think I got it, it's actually a bit surprising and I didn't expect that: The 100ms sleep is causing the delay, if you change it down to 10ms runtime goes to where it was before. |
Awesome find! Surprising that I didn't notice it when running it locally. |
Let's close it and reopen if issue resurfaces. |
https://github.com/etcd-io/etcd/runs/7499725943?check_suite_focus=true
Interesting log:
The text was updated successfully, but these errors were encountered: