Closed Bug 893715 Opened 11 years ago Closed 10 years ago

Intermittent TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Test timed out

Categories

(DevTools :: General, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

https://tbpl.mozilla.org/php/getParsedLog.php?id=25274566&tree=Mozilla-Inbound

Windows 7 32-bit mozilla-inbound debug test mochitest-browser-chrome on 2013-07-14 08:42:57 PDT for push fa6ef0b63025

slave: t-w732-ix-115

09:24:59  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Test timed out
09:25:00  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Found a devtools:scratchpad after previous test timed out
09:25:00  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Found a devtools:scratchpad after previous test timed out
09:25:00  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Found a devtools:scratchpad after previous test timed out
09:25:00  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Found a devtools:scratchpad after previous test timed out
09:25:00  WARNING -  TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Found a  after previous test timed out
Assignee: wbamberg → nobody
Product: Developer Documentation → Firefox
The reason that the test times out appears to be some WebGL / Tilt Error:
12:59:52 browser_telemetry_buttonsandsidebar.js | Console message: [JavaScript Warning: "Error: WebGL: Error during ANGLE OpenGL ES initialization" {file: "resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/tilt/tilt-gl.js" line: 1580}]
12:59:52     INFO -  TEST-INFO | chrome://mochitests/content/browser/browser/devtools/shared/test/browser_telemetry_buttonsandsidebar.js | Console message: [JavaScript Error: "Failure"]
The above warning seems to trigger a dialog containing the following:
"Could not initialize tilt, please check the troubleshooting information at http://get.webgl.org/troubleshooting"

Looking at the screenshot I suspect that WebGL is not available on that test box?

Victor is our WebGL Rockstar so he will most likely have a better insight.
Attachment #777073 - Flags: feedback?(vporof)
In fact, this is probably confirmed:
WARNING: Direct3D 9-accelerated layers are not supported on this system.: file e:/builds/moz2_slave/m-in-w32-d-0000000000000000000/build/gfx/layers/d3d9/LayerManagerD3D9.cpp, line 54
The funny thing about WebGL is that it sometimes fails spectacularly when it's not supported. I'm not entirely familiar with browser_telemetry_buttonsandsidebar.js, but from what I see it seems like Tilt is opened but the case in which WebGL isn't available isn't entirely handled. 

Tilt tests go a long way to ensure crazy things don't happen. In head.js, there's a function called isWebGLSupported which checks if the tests should continue or not.

There are a few ways to determine if WebGL is enabled and works:
1. it is forced to be enabled (usually a bad thing, via webgl.force-enabled pref)
2. it's supported (querying stuff in nsIGfxInfo, see isWebGLSupported in tilt-gl.js)
3. creating a canvas with a webgl context doesn't throw or return null

Any combination of the above three could determine if WebGL works or not, but the only definitive way of being sure is for 2. and 3. to be true. If 1. is true, then crazy things can happen.
Attachment #777073 - Flags: feedback?(vporof)
Thanks, either way WebGL should be available on test boxes.
What is really strange is that this does not occur every time ... I suspect either an issue with the test box or another patch.

Let's wait and see what happens.
This is not a bug on our side but an issue with some of the Win 7 test machines and either their hardware or drivers.

See bug 873566 for more information.
Closing inactive keywords:intermittent-failure bugs where the TBPLbot has previously commented and the test isn't marked as disabled; filter on orange-cleanup-201401.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: