Closed Bug 558579 Opened 14 years ago Closed 12 years ago

Intermittent mochitest-plain 1/5 crash running content/html/content/test/test_bug332893-1.html

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tnikkel, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1270928829.1270929137.17607.gz
Rev3 Fedora 12x64 mozilla-central opt test mochitests-1/5 on 2010/04/10 12:47:09
s: talos-r3-fed64-006
TEST-UNEXPECTED-FAIL | automation.py | Exited with code 11 during test run
PROCESS-CRASH | automation.py | application crashed (minidump found)

33962 INFO Running /tests/content/html/content/test/test_bug332893-1.html...
TEST-UNEXPECTED-FAIL | automation.py | Exited with code 11 during test run
INFO | automation.py | Application ran for: 0:01:39.950483
INFO | automation.py | Reading PID log: /tmp/tmpBN5oOqpidlog
==> process 2058 launched child process 2181
INFO | automation.py | Checking for orphan process with PID: 2181
PROCESS-CRASH | automation.py | application crashed (minidump found)
MINIDUMP_STACKWALK binary not found: /home/cltbld/talos-slave/mozilla-central-fedora64-opt-u-mochitests-1/tools/breakpad/linux64/minidump_stackwalk
WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks can't be detected!

INFO | runtests.py | Running tests: end.
program finished with exit code 11
elapsedTime=102.867853
TinderboxPrint: mochitest-plain-1<br/><em class="testfail">T-FAIL</em>
Unknown Error: command finished with exit code: 11
=== Output ended ===
======== BuildStep ended ========
======== BuildStep started ========
maybe rebooting slave lost
=== Output ===
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
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.