New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 598835 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 590951
Owner:
OOO until 2019-01-24
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

WebglConformance.conformance_attribs_gl_disabled_vertex_attrib failing on https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20(New%20Intel)

Project Member Reported by jbau...@chromium.org, Mar 29 2016

Issue description

https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/23/steps/webgl_conformance_gl_tests/logs/stdio has

[ RUN      ] WebglConformance.conformance_attribs_gl_disabled_vertex_attrib
[1808:3664:0328/171846:INFO:CONSOLE(11)] "Unable to fetch WebGL rendering context for Canvas", source:  (11)
[1808:3664:0328/171846:INFO:CONSOLE(11)] "FAIL Unable to fetch WebGL rendering context for Canvas", source:  (11)
[1808:3664:0328/171846:INFO:CONSOLE(11)] "Uncaught TypeError: Cannot read property 'getParameter' of null", source:  (11)
[1808:3664:0328/171846:INFO:CONSOLE(70)] "Uncaught TypeError: Cannot read property 'getParameter' of null", source: http://127.0.0.1:51744/conformance/attribs/gl-disabled-vertex-attrib.html (70)
[1808:3664:0328/171846:INFO:CONSOLE(11)] "successfullyParsed should be true (of type boolean). Was undefined (of type undefined).", source:  (11)
[1808:3664:0328/171846:INFO:CONSOLE(11)] "FAIL successfullyParsed should be true (of type boolean). Was undefined (of type undefined).", source:  (11)
Traceback (most recent call last):
  File "c:\users\chrome~1.lab\appdata\local\temp\isolated_run4icxnb\third_party\catapult\telemetry\telemetry\internal\story_runner.py", line 84, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "c:\users\chrome~1.lab\appdata\local\temp\isolated_run4icxnb\content\test\gpu\gpu_tests\gpu_test_base.py", line 122, in RunStory
    RunStoryWithRetries(DesktopGpuSharedPageState, self, results)
  File "c:\users\chrome~1.lab\appdata\local\temp\isolated_run4icxnb\content\test\gpu\gpu_tests\gpu_test_base.py", line 72, in RunStoryWithRetries
    super(cls, shared_page_state).RunStory(results)
  File "c:\users\chrome~1.lab\appdata\local\temp\isolated_run4icxnb\third_party\catapult\telemetry\telemetry\page\shared_page_state.py", line 338, in RunStory
    self._current_page, self._current_tab, results)
  File "c:\users\chrome~1.lab\appdata\local\temp\isolated_run4icxnb\content\test\gpu\gpu_tests\webgl_conformance.py", line 78, in ValidateAndMeasurePage
    raise page_test.Failure(_WebGLTestMessages(tab))
Failure: Unable to fetch WebGL rendering context for Canvas
FAIL Unable to fetch WebGL rendering context for Canvas
Uncaught TypeError: Cannot read property 'getParameter' of null
successfullyParsed should be true (of type boolean). Was undefined (of type undefined).
FAIL successfullyParsed should be true (of type boolean). Was undefined (of type undefined).


[  FAILED  ] WebglConformance.conformance_attribs_gl_disabled_vertex_attrib (354 ms)

This seems to have started at https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/23 so I'm suspecting https://chromium.googlesource.com/chromium/src/+/d4100e5324db5db722c4c1de3f1edaed76d6b137
 

Comment 1 by kbr@chromium.org, Mar 30 2016

Cc: geoffl...@chromium.org
Interesting that it's only this new bot that was affected but we should get it back to a green state ASAP as this might indicate a more pervasive problem.

Comment 2 by danakj@chromium.org, Mar 30 2016

Status: Started (was: Assigned)
So weird that it was this CL, most unexpected. Any advice on reproing on NVIDIA? >_>

Comment 3 by danakj@chromium.org, Mar 30 2016

Cc: kbr@chromium.org

Comment 4 by danakj@chromium.org, Mar 30 2016

Cc: zmo@chromium.org

Comment 5 by kbr@chromium.org, Mar 30 2016

The change is probably taking a slightly different code path down Intel's OpenGL driver.

geofflang@ would be the best person to help advise.

Sorry, looks like this probably isn't caused by https://chromium.googlesource.com/chromium/src/+/d4100e5324db5db722c4c1de3f1edaed76d6b137 after all. https://build.chromium.org/p/chromium.gpu.fyi/builders/Win7%20Release%20%28New%20Intel%29/builds/22 didn't actually run the webgl tests, so it's possible this bot was broken since it was set up. It looks like the GPU process always fails to initialize.

Comment 7 by danakj@chromium.org, Mar 30 2016

Owner: kbr@chromium.org
Status: Assigned (was: Started)
Ooooh okay. => kbr?

Comment 8 by kbr@chromium.org, Mar 30 2016

Mergedinto: 590951
Status: Duplicate (was: Assigned)
Oops. Sorry about that. These bots have the same problem as the earlier Win Intel bots and we need to skip this step on them. Let me dupe this into the earlier bug and stop running the step entirely on these new bots.

Sign in to add a comment