Closed Bug 690657 Opened 13 years ago Closed 12 years ago

Intermittent browser_tabview_bug649006.js, browser_tabview_bug610242.js, browser_tabview_bug656913.js, browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output

Categories

(Firefox Graveyard :: Panorama, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

+++ This bug was initially created as a clone of Bug #649127 +++ https://tbpl.mozilla.org/php/getParsedLog.php?id=6620698&tree=Mozilla-Inbound Rev3 WINNT 5.1 mozilla-inbound opt test mochitest-other on 2011-09-29 21:23:02 PDT for push 9ef649a80d93 TEST-START | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_rtl.js TEST-PASS | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_rtl.js | Tab View starts hidden TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/tabview/browser_tabview_rtl.js | application timed out after 330 seconds with no output (and a stack, no idea if it's a helpful one anywhere)
Summary: Intermittent timeout in browser/base/content/test/tabview/browser_tabview_rtl.js | application timed out after 330 seconds with no output → Intermittent browser_tabview_rtl.js, browser_tabview_bug634077.js | application timed out after 330 seconds with no output
Summary: Intermittent browser_tabview_rtl.js, browser_tabview_bug634077.js | application timed out after 330 seconds with no output → Intermittent browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output
Summary: Intermittent browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output → Intermittent browser_tabview_bug656913.js, browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output
Summary: Intermittent browser_tabview_bug656913.js, browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output → Intermittent browser_tabview_bug610242.js, browser_tabview_bug656913.js, browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output
Summary: Intermittent browser_tabview_bug610242.js, browser_tabview_bug656913.js, browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output → Intermittent browser_tabview_bug649006.js, browser_tabview_bug610242.js, browser_tabview_bug656913.js, browser_tabview_rtl.js, browser_tabview_bug634077.js, browser_tabview_bug631752.js | application timed out after 330 seconds with no output
Comments 9 and 10 are actually a crash under LayerManagerD3D10::Render() ("Exited with code 253"), rather than the original timeout described in this bug. I've filed the crash separately as bug 747622.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.