Intermittent TEST-UNEXPECTED-FAIL | /tests/dom/plugins/test/test_pluginstream_seek.html | application timed out after 330 seconds with no output

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
8 years ago
7 years ago

People

(Reporter: mbrubeck, Unassigned)

Tracking

({intermittent-failure})

11 Branch
x86_64
macOS
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [test which aborts the suite])

Reporter

Description

8 years ago
The screenshot shows the mochitest harness; everything looks normal.  The "Lorem ipsum" text and a box containing the Firefox User-Agent string are visible in the test frame.

https://tbpl.mozilla.org/php/getParsedLog.php?id=7472012&tree=Mozilla-Inbound
Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound opt test mochitests-2/5 on 2011-11-18 09:24:51 PST for push 2ccba9e140f2

6002 INFO TEST-PASS | /tests/dom/plugins/test/test_pluginstream_poststream.html | plugin reported error - pass should equal pass
6003 INFO TEST-END | /tests/dom/plugins/test/test_pluginstream_poststream.html | finished in 218ms
6004 INFO TEST-START | /tests/dom/plugins/test/test_pluginstream_seek.html
TEST-UNEXPECTED-FAIL | /tests/dom/plugins/test/test_pluginstream_seek.html | application timed out after 330 seconds with no output
args: ['/usr/sbin/screencapture', '-C', '-x', '-t', 'png', '/var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/mozilla-test-fail_Zawg2I']

Can't trigger Breakpad, just killing process
INFO | automation.py | Application ran for: 0:07:34.529294
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmphlld4Ppidlog
WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks can't be detected!

INFO | runtests.py | Running tests: end.
program finished with exit code 247
elapsedTime=457.449098
Comment hidden (Legacy TBPL/Treeherder Robot)
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange][test which aborts the suite] → [test which aborts the suite]
You need to log in before you can comment on or make changes to this bug.