605716 - TEST-UNEXPECTED-FAIL | reftest/tests/layout/base/crashtests/266360-1.html | application timed out after 330 seconds with no output

Status: RESOLVED WORKSFORME

(Core :: Layout, defect)

Description

[Josh Matthews [:jdm]]

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1287547990.1287549710.17861.gz
WINNT 5.2 mozilla-central debug test crashtest on 2010/10/19 21:13:10

s: mw32-ix-slave11
TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/266360-1.html | application timed out after 330 seconds with no output
buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output

Comment 1

[Legacy TBPL/Treeherder Robot]

philringnalda%gmail.com
http://tinderbox.mozilla.org/showlog.cgi?log=TraceMonkey/1288310423.1288312431.19168.gz
WINNT 5.2 tracemonkey debug test crashtest on 2010/10/28 17:00:23

s: win32-slave13
TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/tracemonkey-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/266360-1.html | application timed out after 330 seconds with no output
buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output

Comment 2

[Legacy TBPL/Treeherder Robot]

philringnalda%gmail.com
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1288556111.1288557851.23985.gz
WINNT 5.2 mozilla-central debug test crashtest on 2010/10/31 13:15:11

s: win32-slave05
REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/143862-1c.html | timed out waiting for onload to fire
REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/266360-1.html | timed out waiting for onload to fire

Comment 3

[Legacy TBPL/Treeherder Robot]

ehsan%mozilla.com
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1291842513.1291844305.20097.gz
WINNT 5.2 mozilla-central debug test crashtest on 2010/12/08 13:08:33

s: mw32-ix-slave05
TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/266360-1.html | application timed out after 330 seconds with no output
buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output

Comment 4

[Legacy TBPL/Treeherder Robot]

josh%joshmatthews.net
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1292444185.1292446169.3014.gz
WINNT 5.2 mozilla-central debug test crashtest on 2010/12/15 12:16:25

s: mw32-ix-slave05
TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/test/build/reftest/tests/layout/base/crashtests/266360-1.html | application timed out after 330 seconds with no output
buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output

Comment 5

[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