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
Triage chrome on android issues #13233
Labels
P2
A bug or feature request we're likely to work on
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
web-dart2js
Comments
+dgrove cc @dgrove. |
Added this to the M7 milestone. |
We're still seeing somewhat random timeouts on the Chrome-on-Android build bots. Removed the owner. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
kevmoo
added
P2
A bug or feature request we're likely to work on
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
and removed
Priority-Medium
labels
Mar 1, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P2
A bug or feature request we're likely to work on
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
web-dart2js
We have 42 failing tests on chrome on android.
Would be good if the dart2js team could triage these so that we can move the phones/vm to the main waterfall - it has been sitting there for almost 4 months and was at the time considered critical.
See:
http://build.chromium.org/p/client.dart.fyi/builders/dart2js-chromeOnAndroid-linux/
This is running chrome 26, I filed issue #13232 to update this to 29 (but most of the stuff there is probably not related to this)
The text was updated successfully, but these errors were encountered: