-
Notifications
You must be signed in to change notification settings - Fork 919
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
Oblitirate test flakiness #756
Conversation
86af54d
to
177c1d2
Compare
And to be honest. We are fixing tests and wasting time on tests with zero value to the code coverage. |
Codecov Report
@@ Coverage Diff @@
## main #756 +/- ##
==========================================
+ Coverage 52.67% 52.85% +0.18%
==========================================
Files 116 116
Lines 6574 6574
==========================================
+ Hits 3463 3475 +12
+ Misses 2748 2740 -8
+ Partials 363 359 -4
Continue to review full report at Codecov.
|
I rerun tests 3 times already, and all of them pass |
Forth run, one guy failed, fixing him |
2946a86
to
1e4db49
Compare
Ok, 3 more times, and it passes. Should be enough |
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.
🚢 🚢 🚢 🚢
yes yes yes yes
a6aef54
to
42ff319
Compare
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.
MORGE IT
42ff319
to
7bf68fc
Compare
7bf68fc
to
6dcfbed
Compare
Ok, I accidentally pushed |
With some runtime tricks I was able tor reproduce and fix all the flakes, but this one is not and it makes me insane |
maybe try increasing the timeout there? I think if we rely on timeouts we will always run into some flakines no? |
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.
Changes look gud
The test does not fail because of the timeout. It fails because, for some reason, one test routine is executed after the background routine.
I put global timeouts in general for tests with concurrency. If they deadlock for some flakey or other reason. |
6dcfbed
to
bc56d54
Compare
I think the heightSub test is fixed forever with the time sleep. However #579 showed up again lol |
…estListener to deflake tests
#759 But it is unrelated to this PR so I am merging this |
Fixes #683
Fixes #467
Also, #736 did a good job for us and:
Closes #582
Closes #608
Hopefully closes #584
Hopefully closes #579
Bonus: #476
(it does not really fix this #476, but it fixes the flakeyness that was mixed up with #476, while #476 is another one that was not reproduced for a long time, and I assume it is now fixed)