611808 - Intermittent failure in /tests/dom/tests/mochitest/bugs/test_bug260264_nested.html | application timed out after 330 seconds with no output

Status: RESOLVED WORKSFORME

(Core :: General, defect)

Description

[alexander :surkov (:asurkov)]

TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/bugs/test_bug260264_nested.html | application timed out after 330 seconds with no output
Can't trigger Breakpad, just killing process
INFO | automation.py | Application ran for: 0:10:40.772136
INFO | automation.py | Reading PID log: /var/folders/Xr/Xr--yJnSEY0U11ET5NZuMU+++TM/-Tmp-/tmpheHP7_pidlog
PROCESS-CRASH | /tests/dom/tests/mochitest/bugs/test_bug260264_nested.html | application crashed (minidump found)
stderr from minidump_stackwalk:
2010-11-12 12:14:50: minidump_processor.cc:264: INFO: Processing minidump in file /var/folders/Xr/Xr--yJnSEY0U11ET5NZuMU+++TM/-Tmp-/tmpuEXWyO/minidumps/A600D041-8C54-48CE-A90F-EA840D64B737.dmp
2010-11-12 12:14:50: minidump.cc:3500: INFO: Minidump opened minidump /var/folders/Xr/Xr--yJnSEY0U11ET5NZuMU+++TM/-Tmp-/tmpuEXWyO/minidumps/A600D041-8C54-48CE-A90F-EA840D64B737.dmp
2010-11-12 12:14:50: minidump.cc:3532: ERROR: Minidump header signature mismatch: (0x0, 0x0) != 0x504d444d
2010-11-12 12:14:50: minidump_processor.cc:268: ERROR: Minidump /var/folders/Xr/Xr--yJnSEY0U11ET5NZuMU+++TM/-Tmp-/tmpuEXWyO/minidumps/A600D041-8C54-48CE-A90F-EA840D64B737.dmp could not be read
2010-11-12 12:14:50: minidump.cc:3472: INFO: Minidump closing minidump
2010-11-12 12:14:50: minidump_stackwalk.cc:509: ERROR: MinidumpProcessor::Process failed

minidump_stackwalk exited with return code 1
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

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1289592131.1289592920.16674.gz&fulltext=1#err0

Comment 1

[Ed Morley [:emorley]]

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