Fix flaky test in MainLooperLongTaskStrategyTest#1730
Merged
Conversation
0xnm
approved these changes
Nov 17, 2023
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #1730 +/- ##
===========================================
- Coverage 83.41% 83.37% -0.04%
===========================================
Files 465 465
Lines 16173 16170 -3
Branches 2407 2406 -1
===========================================
- Hits 13490 13481 -9
- Misses 2027 2028 +1
- Partials 656 661 +5 |
mariusc83
approved these changes
Nov 17, 2023
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
4 participants
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 does this PR do?
Fix a flaky test in MainLooperLongTaskStrategyTest.
Flakiness arise from the way multithreading can introduce some delays, and some suboptimal assertions:
Thread.sleep(duration + 1), which is a bit weird..isCloseTo(duration, offset), which would be the same as.isBetween(duration - offset, duration + offset). This assertion is not perfect as a detected value less than duration is impossible, and wrong..isBetween(duration, duration + 16L)Note
Although this reduces drastically the flakiness of this test, it can sometimes happen (once every 1000 run or so) that a GC or other stuff will delay the test run, and result in a failing test.