Closed Bug 942619 Opened 12 years ago Closed 11 years ago

Intermittent browser_600545.js | Test timed out, two found a tab, one found a window, browser_601955.js | first tab should not be pinned yet

Categories

(Firefox :: Session Restore, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=31020424&tree=Mozilla-Inbound Rev4 MacOSX Lion 10.7 mozilla-inbound opt test mochitest-browser-chrome on 2013-11-24 12:03:48 PST for push cf058c8a3b63 slave: talos-r4-lion-040 12:15:16 INFO - TEST-START | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js 12:15:16 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: OpenGL compositor Initialized Succesfully. 12:15:16 INFO - Version: 2.1 NVIDIA-7.12.9 12:15:16 INFO - Vendor: NVIDIA Corporation 12:15:16 INFO - Renderer: NVIDIA GeForce 320M OpenGL Engine 12:15:16 INFO - FBO Texture Target: TEXTURE_2D 12:15:16 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.com/#1" line: 0}] 12:15:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.org/#0" line: 0}] 12:15:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.com/#2" line: 0}] 12:15:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.com/#3" line: 0}] 12:15:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.com/#4" line: 0}] 12:15:17 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "http://example.com/#6" line: 0}] (screenshot) 12:15:56 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Test timed out 12:15:56 INFO - TEST-INFO | MEMORY STAT vsize after test: 3914399744 12:15:56 INFO - TEST-INFO | MEMORY STAT residentFast after test: 568197120 12:15:56 INFO - TEST-INFO | MEMORY STAT heapAllocated after test: 142695752 12:15:56 INFO - INFO TEST-END | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | finished in 30086ms 12:15:56 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Found a tab after previous test timed out: http://example.com/#2 12:15:56 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Found a tab after previous test timed out: http://example.com/#1 12:15:56 INFO - TEST-INFO | checking window state 12:15:56 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | Found a browser window after previous test timed out 12:15:56 INFO - TEST-INFO | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_600545.js | must wait for focus 12:15:56 INFO - TEST-START | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_601955.js 12:15:56 WARNING - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_601955.js | first tab should not be pinned yet 12:15:56 INFO - Stack trace: 12:15:56 INFO - JS frame :: chrome://mochitests/content/browser/browser/components/sessionstore/test/browser_601955.js :: testBug601955_1 :: line 24 12:15:56 INFO - JS frame :: chrome://mochitests/content/browser/browser/components/sessionstore/test/head.js :: <TOP_LEVEL> :: line 211 12:15:56 INFO - JS frame :: chrome://mochikit/content/browser-test.js :: testScope/test_executeSoon/<.run :: line 734 12:15:56 INFO - native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
According to the logs, the content process is crashing here. Only happening on inbound for now, I wonder if a changeset introduced something fragile.
FTR, this bug was basically dead before, didn't occur for 8 months.
Filed bug 1139822 for the new incarnation of this bug. This specific failure didn't occur for 8+ months, closing.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.