Skip to content
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

Jump to bottom

Various tests time out flakily on chromeOnAndroid #15610

Closed
whesse opened this issue Dec 12, 2013 · 1 comment
Closed

Various tests time out flakily on chromeOnAndroid #15610

whesse opened this issue Dec 12, 2013 · 1 comment
Assignees
@whesse
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@whesse
Copy link
Member

whesse commented Dec 12, 2013

This test timed out, at http://build.chromium.org/p/client.dart.fyi/builders/dart2js-chromeOnAndroid-linux-be/builds/1103/steps/dart2js-chromeOnAndroid%20tests%20failures/logs/stdio

On other runs, the test doesn't take a large amount of time, so this is a flaky bug, not a slow-running test, probably.
@whesse
Copy link
Member Author

whesse commented Dec 12, 2013

Also mirrors/invoke_subscript_test timed out, instead of having a RuntimeError.

It may be that any test can randomly timeout - I am adding them to this bug, until we can see if there are problems with these particular tests, or not.

Set owner to @whesse.
Removed Area-Dart2JS label.
Added Area-Infrastructure label.
Changed the title to: "Various tests time out flakily on chromeOnAndroid".

@whesse whesse added Type-Defect area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. labels Dec 12, 2013
@whesse whesse self-assigned this Dec 12, 2013
@kevmoo 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 triaged labels Feb 29, 2016
@athomas athomas added the closed-obsolete Closed as the reported issue is no longer relevant label Jul 2, 2019
@athomas athomas closed this as completed Jul 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@whesse whesse

Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kevmoo @whesse @athomas