570402 - TEST-UNEXPECTED-FAIL | automation.py | Exited with code 11 during test run [@ 0x1 | nsXBLBinding::InstallEventHandlers]; during/after test chrome/toolkit/components/places/tests/chrome/test_341972a.xul

Status: RESOLVED WORKSFORME

(Core :: XBL, defect)

Description

[Mats Palmgren (inactive)]

Linux mozilla-central opt test mochitest-other on 2010/06/06 03:28:32
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1275820112.1275820936.30044.gz

s: moz2-linux-slave05
TEST-UNEXPECTED-FAIL | automation.py | Exited with code 11 during test run

chrome/toolkit/components/places/tests/chrome/test_341972a.xul

Stack:
0x1
nsXBLBinding::InstallEventHandlers
nsXBLService::LoadBindings
nsCSSFrameConstructor::AddFrameConstructionItemsInternal
nsCSSFrameConstructor::AddFrameConstructionItems
nsCSSFrameConstructor::ProcessChildren
...

Comment 1

[Mats Palmgren (inactive)]

Attachment: Crash backtrace

Comment 2

[Mats Palmgren (inactive)]

The build above was for this changeset:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5f2e4510a213&tochange=ac1ed3f6b2e7

Comment 3

[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