Closed Bug 832922 Opened 12 years ago Closed 7 years ago

timeout during test_garbage_at_end_of_declarations.html and other weirdness with b2g mochitest timeouts

Categories

(Core :: CSS Parsing and Computation, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: dbaron, Unassigned)

Details

This B2G emulator mochitest run: https://tbpl.mozilla.org/php/getParsedLog.php?id=18982837&tree=Mozilla-Inbound shows a timeout running test_garbage_at_end_of_declarations. (The log is actually a little interesting. My interpretation of it is that there's a bunch of stuff from the side that's driving the device (which I'll call parent, but I'm not really sure what it is), and then there's a logcat from the device itself, and they actually show somewhat different errors.) What looks to me like the parent side says: 02:11:47 WARNING - TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_garbage_at_end_of_declarations.html | application timed out after 330 seconds with no output but the logcat output has: 02:15:54 INFO - I/GeckoDump( 847): 16648 ERROR TEST-UNEXPECTED-FAIL | /tests/layout/style/test/test_garbage_at_end_of_declarations.html | Test timed out. after which the test just keeps on running until: 02:15:54 INFO - I/GeckoDump( 847): 16756 INFO TEST-END | /tests/layout/style/test/test_garbage_at_end_of_declarations.html | finished in 376880ms 02:15:54 INFO - I/GeckoDump( 847): 16757 INFO TEST-START | /tests/layout/style/test/test_html_attribute_computed_values.html but then the test even *keeps* running, simultaneously with other tests (but the parent never finds out about any of this). The obvious fix seems to be to do what we can to make this test run faster... but there also seems to be something pretty broken with the harness here.
Mass closing as we are no longer working on b2g/firefox os.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Mass closing as we are no longer working on b2g/firefox os.
You need to log in before you can comment on or make changes to this bug.