-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
service/smart_next_test flaking #24176
Labels
Comments
Are the smarts for smart-next in the client or the server? |
Potential fix in https://codereview.chromium.org/1313713003 |
turnidge
added a commit
that referenced
this issue
Aug 24, 2015
…sed. This may be causing bug #24176. [email protected] Review URL: https://codereview.chromium.org//1313713003 .
Committed "fix" in 8ed3777. If we do not see the flaky behavior again soon, we will close this bug. |
|
May be fixed by de300cf. If the bots look clean, then we will close this bug. |
I haven't see any failures on the bots in a few days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We sometimes wind up in Frame(_RootZone.runUnary zone.dart:token(8932)), which would happen if we made a synchronous step where we should have made an asynchronous step. Presumably there is race in getting the latest pause event.
The text was updated successfully, but these errors were encountered: