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

Content_shell test failures on Android. #19127

Closed
whesse opened this issue Jun 2, 2014 · 5 comments
Closed

Content_shell test failures on Android. #19127

whesse opened this issue Jun 2, 2014 · 5 comments
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). 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
Contributor

whesse commented Jun 2, 2014

We now have a public buildbot building content_shell with Dart on Android, and running tests on an attached device. About 40 tests are failing - these should be triaged and individual bugs filed for them (and the bugs fixed).

Adding suppressions to the status files, labeled with this bug number.

@whesse
Copy link
Contributor Author

whesse commented Jun 2, 2014

Here are the status file changes with this issue number:

samples/samples.status:
    third_party/todomvc/test/listorder_test: Pass, RuntimeError, Timeout # Issue #18931, Issue #19127

tests/co19/co19-dartium.status:
    LibTest/html/Element/getBoundingClientRect_A01_t02: RuntimeError # Issue #19127.

tests/html/html.status:
    html/mouse_event_test: Skip # Times out. Issue #19127
    css_test/supportsPointConversions # Times out. Issue #19127
    canvasrenderingcontext2d_test/drawImage_video_element: RuntimeError # Issue #19127
    canvasrenderingcontext2d_test/drawImage_video_element_dataUrl: RuntimeError # Issue #19127

@a-siva
Copy link
Contributor

a-siva commented Jun 9, 2014

Adding couple of more tests to the status file as they are timing out too.
websocket_test/websocket: Skip # Times out. Issue #19127
element_offset_test/offset: Skip # Issue #19127, 17550

@whesse
Copy link
Contributor Author

whesse commented Jun 10, 2014

Copying the timeouts from issue #19276 to this issue, and closing 19276.

Adding two new timeouts:
html/typed_arrays_range_checks_test
html/websocket_test/supported

Copied from 19276
Always time out:
html/css_test/functional
html/blob_constructor_test

timed out more than once:
isolate/nested_spawn2_test
lib/mirrors/mirrors_reader_test
language/function_subtype_local1_test

only timed out once:
language/closure7_test
language/abstract_exact_selector_test/01
lib/mirrors/lazy_static_test

@whesse
Copy link
Contributor Author

whesse commented Jun 10, 2014

Issue #19276 has been merged into this issue.

@whesse
Copy link
Contributor Author

whesse commented Jun 16, 2014

Some of these timeouts were due to the tests running after
html/audiocontext_test/functional and
html/audiobuffersourcenode_test/functional.

These two tests make whatever test follows them on the phone, hang.

Removing the timeout marker from

html/typed_arrays_range_checks_test
html/websocket_test/supported
html/websocket_test/websocket
html/blob_constructor_test
html/css_test/functional
history_test/supported_state
indexeddb_5_test

Leaving the skip for
element_offset_test/offset: Skip # Issue #19127, 17550

Adding skips for
lib/mirrors/deferred_mirrors_metadata_test: Skip # Times out. Issue #19129
lib/mirrors/deferred_mirrors_metatarget_test: Fail # Issue #16898
and
html/audiocontext_test/functional
html/audiobuffersourcenode_test/functional

@whesse whesse added area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). Priority-Medium labels Jun 16, 2014
@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 Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-meta Cross-cutting, high-level issues (for tracking many other implementation issues, ...). 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
Development

No branches or pull requests

5 participants