Did a quick triage, not sure what's going on. It doesn't look like the GPU process crashed or anything like that. Test rendered almost solid black instead of the intended color.

If we add "flaky" suppressions for these tests then let's keep them as narrow as possible (i.e., just for this card).

From https://luci-milo.appspot.com/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%20Quadro%20P400%29/849 :

[983/2668] gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_conformance2_textures_video_tex_3d_rgba32f_rgba_float failed unexpectedly 3.1000s:
  
  Traceback (most recent call last):
    _RunGpuTest at content\test\gpu\gpu_tests\gpu_integration_test.py:76
      self.RunActualGpuTest(url, *args)
    RunActualGpuTest at content\test\gpu\gpu_tests\webgl_conformance_integration_test.py:203
      getattr(self, test_name)(test_path, *args[1:])
    _RunConformanceTest at content\test\gpu\gpu_tests\webgl_conformance_integration_test.py:217
      self._CheckTestCompletion()
    _CheckTestCompletion at content\test\gpu\gpu_tests\webgl_conformance_integration_test.py:213
      self.fail(self._WebGLTestMessages(self.tab))
    fail at C:\b\depot_tools\python276_bin\lib\unittest\case.py:412
      raise self.failureException(msg)
  AssertionError: shouldBe 0,255,0
  at (4, 4) expected: 0,255,0 was 1,0,1

Maybe caused by https://codereview.chromium.org/2859723002/ , though webgl_conformance_d3d9_tests failed once, which seems like it shouldn't be related. I can't seem to repro this on my NVIDIA computer.

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

commit 998756bd26860b4abf69221271f74fcf6cf47198
Author: Kai Ninomiya <kainino@chromium.org>
Date: Tue Jun 06 21:23:02 2017

Add expectations for issue 728670

Broadens webgl2 flaky expectations to video/* and image_bitmap_from_video/*.

Tightens both webgl and webgl2 to d3d11 only (should work).

TBR=kbr@chromium.org
NOTRY=true

Bug: 728670
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;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
Change-Id: I767cbe9925beb519f9a7ad0a3b681e39245a2928
Reviewed-on: https://chromium-review.googlesource.com/526315
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#477407}
[modify] https://crrev.com/998756bd26860b4abf69221271f74fcf6cf47198/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
[modify] https://crrev.com/998756bd26860b4abf69221271f74fcf6cf47198/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Expanded the expectations to try to clear up redness on the FYI bots.

oops, realized I added d3d11 in more places than needed. will fix.

I'm experiencing the same error with the nvidia quadro nvs 450, webgl seems to be working fine other than the fact that it loads some graphics as completely black. Is there a fix for this?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot