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

Issue 678382 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 680684
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocking:
issue 603906



Sign in to add a comment

WebglConformance_conformance_uniforms_gl_uniform_arrays flaky on Win10 Debug (New Intel) GPU.FYI

Project Member Reported by ynovikov@chromium.org, Jan 4 2017

Issue description

https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/171
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/170
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/168
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/167
But also happened before:
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/143
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/141
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/139
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/127

Here is a log from https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Debug%20%28New%20Intel%29/builds/171/steps/webgl_conformance_tests/logs/stdio

WebglConformance_conformance_uniforms_gl_uniform_arrays (gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest) ... [5224:6032:0104/122033.180:INFO:CONSOLE(248)] "WebGL: INVALID_OPERATION: uniform1fv: location is not from current program", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (248)
[5224:6032:0104/122033.181:INFO:CONSOLE(253)] "WebGL: INVALID_VALUE: uniform1fv: no array", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (253)
[4440:320:0104/122033.211:ERROR:gles2_cmd_decoder.cc(8880)] [.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform2fv: wrong uniform function for type
[5224:6032:0104/122033.252:INFO:CONSOLE(248)] "WebGL: INVALID_OPERATION: uniform2fv: location is not from current program", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (248)
[5224:6032:0104/122033.254:INFO:CONSOLE(253)] "WebGL: INVALID_VALUE: uniform2fv: invalid size", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (253)
[5224:6032:0104/122033.255:INFO:CONSOLE(257)] "WebGL: INVALID_VALUE: uniform2fv: invalid size", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (257)
[4440:320:0104/122033.284:ERROR:gles2_cmd_decoder.cc(8880)] [.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type
[5224:6032:0104/122033.320:INFO:CONSOLE(248)] "WebGL: INVALID_OPERATION: uniform3fv: location is not from current program", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (248)
[5224:6032:0104/122033.321:INFO:CONSOLE(253)] "WebGL: INVALID_VALUE: uniform3fv: invalid size", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (253)
[5224:6032:0104/122033.323:INFO:CONSOLE(257)] "WebGL: INVALID_VALUE: uniform3fv: invalid size", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (257)
[4440:320:0104/122033.352:ERROR:gles2_cmd_decoder.cc(8880)] [.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type
[5224:6032:0104/122033.387:INFO:CONSOLE(248)] "WebGL: INVALID_OPERATION: uniform4fv: location is not from current program", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (248)
[5224:6032:0104/122033.388:INFO:CONSOLE(253)] "WebGL: INVALID_VALUE: uniform4fv: invalid size", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (253)
[5224:6032:0104/122033.389:INFO:CONSOLE(257)] "WebGL: INVALID_VALUE: uniform4fv: invalid size", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (257)
[4440:320:0104/122033.418:ERROR:gles2_cmd_decoder.cc(8880)] [.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type
[5224:6032:0104/122051.603:INFO:CONSOLE(0)] "[.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform2fv: wrong uniform function for type", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (0)
[5224:6032:0104/122051.604:INFO:CONSOLE(0)] "[.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (0)
[5224:6032:0104/122051.605:INFO:CONSOLE(0)] "[.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (0)
[5224:6032:0104/122051.606:INFO:CONSOLE(0)] "[.Offscreen-For-WebGL-2A02B568]GL ERROR :GL_INVALID_OPERATION : glUniform1fv: wrong uniform function for type", source: http://127.0.0.1:55944/third_party/webgl/src/sdk/tests/conformance/uniforms/gl-uniform-arrays.html (0)

Traceback (most recent call last):
  _RunGpuTest at content\test\gpu\gpu_tests\gpu_integration_test.py:78
    self.RunActualGpuTest(url, *args)
  RunActualGpuTest at content\test\gpu\gpu_tests\webgl_conformance_integration_test.py:196
    getattr(self, test_name)(test_path, *args[1:])
  _RunConformanceTest at content\test\gpu\gpu_tests\webgl_conformance_integration_test.py:210
    self._CheckTestCompletion()
  _CheckTestCompletion at content\test\gpu\gpu_tests\webgl_conformance_integration_test.py:204
    'webglTestHarness._finished', timeout_in_seconds=300)
  traced_function at third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py:52
    return func(*args, **kwargs)
  WaitForJavaScriptCondition at third_party\catapult\telemetry\telemetry\internal\actions\action_runner.py:246
    self._tab.WaitForJavaScriptExpression(condition, timeout_in_seconds)
  traced_function at third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py:52
    return func(*args, **kwargs)
  WaitForJavaScriptExpression at third_party\catapult\telemetry\telemetry\internal\browser\web_contents.py:143
    e.message + '\n' + debug_message)
TimeoutException: Timed out while waiting 300s for IsJavaScriptExpressionTrue.

If GL errors were relevant, I guess it would always fail and not be flaky? Then something else is causing a timeout?
 

Comment 1 by kbr@chromium.org, Jan 5 2017

Blocking: 603906
Owner: sunn...@chromium.org
Status: Assigned (was: Available)
It sounds to me like the test's aborting abruptly for some reason (maybe an exception?) and that reason isn't being recorded. Did you see any GPU process crashes in the log?

Sunny, could you please mark this as flaky on Win Intel Debug? The line in src/content/test/gpu/gpu_tests/webgl_conformance_expectations.py would be something like:

    # Win / Intel failures
    self.Flaky('conformance/uniforms/gl-uniform-arrays.html',
        ['win', 'debug', 'intel'], bug= 678382 )

Thanks. (Note that per Issue 603906 and related bugs, this might warrant a Skip entry if it continues to fail.)

Project Member

Comment 2 by bugdroid1@chromium.org, Jan 5 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7ddd16d3113540b9ac5b45e6780ebf8487d4c9fa

commit 7ddd16d3113540b9ac5b45e6780ebf8487d4c9fa
Author: sunnyps <sunnyps@chromium.org>
Date: Thu Jan 05 04:30:58 2017

Mark WebglConformance_conformance_uniforms_gl_uniform_arrays as flaky.

TBR=kbr@chromium.org
BUG= 678382 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2612183003
Cr-Commit-Position: refs/heads/master@{#441586}

[modify] https://crrev.com/7ddd16d3113540b9ac5b45e6780ebf8487d4c9fa/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Marking as flaky causes all 3 retries to fail.
And restart after failure prints:
err: rx::Renderer11::initializeD3DDevice(736): Failed creating Debug D3D11 device - falling back to release runtime.

Seems like the bot became more red after this.
Guess the test should be skipped?

Comment 4 by kbr@chromium.org, Jan 6 2017

Yes, please skip it on this configuration only. Thanks.

Project Member

Comment 5 by bugdroid1@chromium.org, Jan 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/589bb071c6344bf7adcf1373577e262d6647c050

commit 589bb071c6344bf7adcf1373577e262d6647c050
Author: ynovikov <ynovikov@chromium.org>
Date: Fri Jan 06 23:47:56 2017

Skip gl_uniform_arrays on Win Debug Intel

Per discussion in the bug

BUG= 678382 
TBR=kbr@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2620563002
Cr-Commit-Position: refs/heads/master@{#442099}

[modify] https://crrev.com/589bb071c6344bf7adcf1373577e262d6647c050/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Owner: kbr@chromium.org
kbr@ can you assign an owner for next steps on this?

Comment 7 by kbr@chromium.org, Jan 10 2017

Cc: yunchao...@intel.com qiankun....@intel.com
Owner: ----
Status: Available (was: Assigned)
I don't have any specific ideas about this one. Let me leave this unowned for now. CC'ing Intel folks in case they can reproduce this flakiness in house.

Comment 8 by kbr@chromium.org, Jan 10 2017

Labels: -Hotlist-PixelWrangler
Cc: jiawei.s...@intel.com yang...@intel.com
Mergedinto: 680684
Status: Duplicate (was: Available)
It should be the same reason as  bug 680684 . This is a slow test and time-out on Debug.

Comment 10 by kbr@chromium.org, Jan 13 2017

Thanks for looking at this Qiankun, but I have some more questions about the test. Please see Issue 603906 (which all of these are now pointing to).

Project Member

Comment 11 by bugdroid1@chromium.org, Jan 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/079ae727092a8011d34ddc6cb3feeb7422bc4a6a

commit 079ae727092a8011d34ddc6cb3feeb7422bc4a6a
Author: qiankun.miao <qiankun.miao@intel.com>
Date: Tue Jan 24 18:05:53 2017

Roll WebGL 9b0c9de..3c655cc

https://chromium.googlesource.com/external/khronosgroup/webgl.git/+log/9b0c9de..3c655cc

BUG=603906, 666384,  678382 ,  673929 ,  682190 ,  684399 

TEST=bots

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2649343002
Cr-Commit-Position: refs/heads/master@{#445758}

[modify] https://crrev.com/079ae727092a8011d34ddc6cb3feeb7422bc4a6a/DEPS
[modify] https://crrev.com/079ae727092a8011d34ddc6cb3feeb7422bc4a6a/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
[modify] https://crrev.com/079ae727092a8011d34ddc6cb3feeb7422bc4a6a/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Sign in to add a comment