This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 473
Intermittent test failure - Dispatchers.Main is used concurrently with setting it #12230
Labels
🎲 intermittent-test
Evil test failures that only happen now-and-then and are a productivity killer
Comments
jonalmeida
added
the
🎲 intermittent-test
Evil test failures that only happen now-and-then and are a productivity killer
label
May 25, 2022
Not sure how a concurrent read-write may happen since we rely on JUnit callback which I expect will ensure the calls about when a test is finished and another one starts are somehow synchronized. |
Similar failures in CI too: #12227 |
Similar failures in CI (PromptFeature again): #12321 |
jonalmeida
added a commit
to jonalmeida/android-components
that referenced
this issue
Jun 13, 2022
Moved to bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1794861 Change performed by the Move to Bugzilla add-on. |
This was referenced Oct 12, 2022
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
🎲 intermittent-test
Evil test failures that only happen now-and-then and are a productivity killer
I saw this while debugging #12143 locally:
@Mugurell do you have any hints about this since you worked on upgrading our coroutine testing recently?
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: