intermittent timeout in reftest/tests/layout/base/crashtests/268157-1.html | application timed out after 330 seconds with no output or timed out waiting for onload to fire

RESOLVED WORKSFORME

Status

()

Core
Layout
RESOLVED WORKSFORME
8 years ago
6 years ago

People

(Reporter: ignoring orange, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Windows Server 2003
intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b8pre) Gecko/20101022 Firefox/4.0b8pre
Build Identifier: 

Filing bug to track random orange.

Reproducible: Sometimes
(Reporter)

Updated

8 years ago
Blocks: 438871
Worse than even me about trying to duck orange bugs :)

That was:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1287837573.1287839461.19586.gz
WINNT 5.2 mozilla-central debug test crashtest on 2010/10/23 05:39:33
s: win32-slave34

REFTEST TEST-START | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/268157-1.html
++DOMWINDOW == 47 (06429848) [serial = 1091] [outer = 03D5EC40]
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850
REFTEST TEST-PASS | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/268157-1.html | (LOAD ONLY)
REFTEST INFO | Loading a blank page
++DOMWINDOW == 48 (053C0F00) [serial = 1092] [outer = 03D5EC40]
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850
(bunch of GC)
TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/268157-1.html | application timed out after 330 seconds with no output

command timed out: 1200 seconds without output
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 7 → Windows Server 2003
Whiteboard: [orange]
Version: unspecified → Trunk
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)

Updated

8 years ago
Summary: intermittent timeout in reftest/tests/layout/base/crashtests/268157-1.html | application timed out after 330 seconds with no output → intermittent timeout in reftest/tests/layout/base/crashtests/268157-1.html | application timed out after 330 seconds with no output or timed out waiting for onload to fire
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)
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
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

6 years ago
Keywords: intermittent-failure
(Assignee)

Updated

6 years ago
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.