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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

zmo, are there any other details here?

I do not repro this bug when I run the test on the latest version of Windows 10.

@zmo, do you still repro? If so, please attach a dxdiag.txt file to the bug so we can try and repro your environment.

Yeah, it's passing on my Win 10 NVidia machine.

Since I didn't input enough details on where I saw the bug originally, let's close this one as fixed.

Let's remove the failure expectation before marking this as fixed. Rafael, I've requested try job access, but it'll be a few days. If you upload a change now I can run the try job for you.

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

commit 726998964292ce7e1f7f860788be3bc52e66c4ea
Author: Rafael Cintron <rafael.cintron@microsoft.com>
Date: Tue Dec 11 20:55:39 2018

Reenable WebGL CT rendering_point_specific_shader_variables.html test

Rendering/point-specific-shader-variables passes on local Windows machine as well as in the lab.

Bug:  616335 
Change-Id: I417062f16edefe784e2723e45919af1af6080ddb
Reviewed-on: https://chromium-review.googlesource.com/c/1370585
Commit-Queue: James Darpinian <jdarpinian@chromium.org>
Reviewed-by: James Darpinian <jdarpinian@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615655}
[modify] https://crrev.com/726998964292ce7e1f7f860788be3bc52e66c4ea/AUTHORS
[modify] https://crrev.com/726998964292ce7e1f7f860788be3bc52e66c4ea/content/test/gpu/gpu_tests/webgl_conformance_expectations.py

Thanks Rafael!