Disable the flaky CalloutController init-order test for now - #1043
Merged
Conversation
myLocation_calledBeforeGeoEngineStarted_resetsActiveFlow_andScopeSurvives fails intermittently on CI with a TimeoutCancellationException waiting on the activeCalloutFlow emissions. The test body dispatches onto the real Dispatchers.Default (no test scheduler controls it), so a loaded runner can miss the 20s bound. Comment out the @test rather than deleting the test, so the code and its rationale stay in the file and it can be re-enabled by restoring the annotation once the wait is made robust. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
myLocation_calledBeforeGeoEngineStarted_resetsActiveFlow_andScopeSurvives fails intermittently on CI with a TimeoutCancellationException waiting on the activeCalloutFlow emissions. The test body dispatches onto the real Dispatchers.Default (no test scheduler controls it), so a loaded runner can miss the 20s bound.
Comment out the @test rather than deleting the test, so the code and its rationale stay in the file and it can be re-enabled by restoring the annotation once the wait is made robust.