Happens in Debug and Release.
Started in https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Release%20%28Intel%20HD%20530%29/builds/942.

Also happens on Intel HD 630:
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Release%20%28Intel%20HD%20630%29/builds/0

Also fails on Nexus 6 starting with
https://build.chromium.org/p/chromium.gpu.fyi/builders/Android%20Release%20%28Nexus%206%29/builds/7797

Going to suppress the test.

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

commit 3dac1e5a910c6e4d1e4cdd2edf342c6549e7464d
Author: Yuly Novikov <ynovikov@chromium.org>
Date: Tue Jun 27 20:41:16 2017

Suppress failing WebGL test

conformance/rendering/clear-after-copyTexImage2D.html
on Win10 Intel WebGL1 and WebGL2 suites
and Nexus 6

New test added in https://codereview.chromium.org/2957683002 WebGL roll

BUG=737002
TBR=zmo@chromium.org

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: I1e083268d0aacfe43d37fb3e28d55d440a48ed50
Reviewed-on: https://chromium-review.googlesource.com/550519
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#482736}
[modify] https://crrev.com/3dac1e5a910c6e4d1e4cdd2edf342c6549e7464d/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
[modify] https://crrev.com/3dac1e5a910c6e4d1e4cdd2edf342c6549e7464d/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Hi Yuly, I wrote this test to expose an Intel D3D driver bug on Intel, and we are trying to fix it now.

Good to know. The course of action should probably be:
1. Fix driver
2. Update driver on bots
3. Re-enable the test

Pity it fails on Nexus 6 as well. Probably will have to keep Fail expectation there.

OK. We will update the status once the new driver with fix is released.

Thank you!

I'd prefer not to own this.

Hi Yuri, 
The next release of Intel D3D driver should fix this bug. We will update the expectation once the fixed driver is released.

Hi all,
Since it is actually a driver bug in Intel D3D driver and cannot work around, shall we lower the priority to P-2 and not block the release of Chrome?

I don't mind if you lower the priority, since the suppression is in place.
But don't you have high priority to fix the driver bug?
Leaving it as is will not get in a way of releasing Chrome, you need ReleaseBlock-* label for that to happen.

OK since this bug won't block chrome release, it isn't necessary to lower the priority.

I must work together with our driver team to fix all the driver bugs, and I can only provide you the public released drivers. Once the driver with fix is released I will update this report.

I see this bug also occurs on Nexus 6, so could you or someone take a look at this?

Actually we have already got fix in our internally-built drivers, so the next released driver will fix this bug.

Hi Yuri,

I have verified the newly released Intel D3D driver can fix this issue:
https://downloadcenter.intel.com/download/27058/Graphics-Intel-Graphics-Driver-for-Windows-15-46-?product=80939

Filed Issue 760263 about upgrading this bot to the latest driver:
https://luci-milo.appspot.com/buildbot/chromium.gpu.fyi/Win10%20Release%20%28Intel%20HD%20630%29/

Downgrading to P2 since the request to upgrade the bot's driver shouldn't be P1.

The bot's been updated to the latest driver starting with this build:
https://luci-milo.appspot.com/buildbot/chromium.gpu.fyi/Win10%20Release%20%28Intel%20HD%20630%29/486

Looking at the most recent build:
https://luci-milo.appspot.com/buildbot/chromium.gpu.fyi/Win10%20Release%20%28Intel%20HD%20630%29/528

and one of the steps on it:
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.gpu.fyi%2FWin10_Release__Intel_HD_630_%2F528%2F%2B%2Frecipes%2Fsteps%2Fscreenshot_sync_tests%2F0%2Fstdout

it's clear that the new driver's running:
INFO:root:  driver_date         : 8-13-2017
INFO:root:  driver_vendor       : Intel Corporation
INFO:root:  driver_version      : 22.20.16.4771

Jiawei, could you take care of turning this test back on?

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

commit 71a01fb96b787da22823cb9d8c214fc31f5cda08
Author: Jiawei Shao <jiawei.shao@intel.com>
Date: Wed Sep 06 18:59:54 2017

Update WebGL / WebGL2 expectations on Windows Intel HD530 / HD630

BUG=chromium:680797, chromium:737002

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: I9be5bbc30d214014a4e5e8a75d17560e4129493b
Reviewed-on: https://chromium-review.googlesource.com/651007
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#500026}
[modify] https://crrev.com/71a01fb96b787da22823cb9d8c214fc31f5cda08/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
[modify] https://crrev.com/71a01fb96b787da22823cb9d8c214fc31f5cda08/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Test doens't fail after CL in #22.
https://build.chromium.org/p/chromium.gpu.fyi/builders/Win10%20Release%20%28Intel%20HD%20630%29/builds/583
Thank you for taking care of this, Jiawei Shao!

I'll keep the bug open for Nexus 6, if someone would like to look at it sometime in the future.

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

Not sure whether we should just close this as WontFix at this point. This device is old and we shouldn't expend a lot of time trying to pass the conformance tests on it.