593257 - [(Debug) Windows SeaMonkey 2.1] crashtest often "randomly" times out

Status: RESOLVED INCOMPLETE

(SeaMonkey :: Testing Infrastructure, defect)

Description

[Serge Gautherie (:sgautherie)]

First occurrence (afaict from still available logs):
http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&maxdate=1279976179&hours=24
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1279965546.1279965729.31134.gz&fulltext=1
WINNT 5.2 comm-central-trunk debug test crashtest on 2010/07/24 02:59:06
{
...
REFTEST TEST-PASS | file:///e:/builds/slave/comm-central-trunk-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/269566-1.html | (LOAD ONLY)
REFTEST INFO | Loading a blank page
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/slave/comm-central-trunk-win32-debug/build/mozilla/docshell/shistory/src/nsSHistory.cpp, line 846
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/slave/comm-central-trunk-win32-debug/build/mozilla/docshell/shistory/src/nsSHistory.cpp, line 846
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/slave/comm-central-trunk-win32-debug/build/mozilla/docshell/shistory/src/nsSHistory.cpp, line 846
WARNING: NS_ENSURE_TRUE(aListener) failed: file e:/builds/slave/comm-central-trunk-win32-debug/build/mozilla/editor/libeditor/base/nsEditor.cpp, line 1714
...
TEST-UNEXPECTED-FAIL | file:///e:/builds/slave/comm-central-trunk-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/269566-1.html | application timed out after 330 seconds with no output
...
TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | missing output line for total leaks!
}

Latest occurence:
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1283453474.1283456003.26977.gz&fulltext=1
WINNT 5.2 comm-central-trunk debug test crashtest on 2010/09/02 11:51:14
{
REFTEST TEST-PASS | file:///e:/builds/slave/comm-central-trunk-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/121533-1.html | (LOAD ONLY)
REFTEST INFO | Loading a blank page
WARNING: NS_ENSURE_TRUE(sf) failed: file e:/builds/slave/comm-central-trunk-win32-debug/build/mozilla/docshell/base/nsDocShell.cpp, line 4882
WARNING: NS_ENSURE_TRUE(sf) failed: file e:/builds/slave/comm-central-trunk-win32-debug/build/mozilla/docshell/base/nsDocShell.cpp, line 4882
TEST-UNEXPECTED-FAIL | file:///e:/builds/slave/comm-central-trunk-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/121533-1.html | application timed out after 330 seconds with no output

command timed out: 1200 seconds without output
}

The test (which/during) which the timeout occurs is not always the same.

Because this test suite was already (perma-)orange and this timeout is random, I can't give a (exact) regression timeframe, nor begin to guess what the cause could be :-(

Comment 1

[Serge Gautherie (:sgautherie)]

Fwiw, this reminds me of bug 497602, bug 509527 and bug 565903:
maybe they have "morphed"?

Comment 2

[Serge Gautherie (:sgautherie)]

And, it looks like these tests (and error) are not listed at
http://brasstacks.mozilla.com/topfails/tests/SeaMonkey :-/

Comment 3

[Jesse Ruderman]

"This test timed out once, and so did this other one" isn't much to go on.  Better luck once bug 589496 is fixed?