Roll WebGL conformance tests to 2cd3af21

Roll WebGL conformance tests to 2cd3af21

BUG=398337
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=288055

[oetuaho-nv, 2014-07-31 14:23:23]

Here's the WebGL roll. I included the OS information from the bots in the
failures list. Is there also some convenient way of finding out which GPUs are
affected?

[Zhenyao Mo, 2014-07-31 19:48:28]

https://codereview.chromium.org/419033012/diff/20001/content/test/gpu/gpu_tes...
File content/test/gpu/gpu_tests/webgl_conformance_expectations.py (right):

https://codereview.chromium.org/419033012/diff/20001/content/test/gpu/gpu_tes...
content/test/gpu/gpu_tests/webgl_conformance_expectations.py:30:
self.Fail('conformance/glsl/misc/shaders-with-uniform-structs.html')
Could you remove the failing tests above
(shaders-with-mis-matching-uniforms.html) as it's passing now?  And set the
bug=351396 to this new entry?

https://codereview.chromium.org/419033012/diff/20001/content/test/gpu/gpu_tes...
content/test/gpu/gpu_tests/webgl_conformance_expectations.py:40: ['win'])
Can you add bug=396058 to this new entry?

https://codereview.chromium.org/419033012/diff/20001/content/test/gpu/gpu_tes...
content/test/gpu/gpu_tests/webgl_conformance_expectations.py:57: ['linux'])
I think if you update this file, you will see a bunch of constructors related
Linux NVIDIA failures.  This one should go together with them, using the same
bug ID.

[Zhenyao Mo, 2014-07-31 19:51:00]

On 2014/07/31 14:23:23, oetuaho-nv wrote:
> Here's the WebGL roll. I included the OS information from the bots in the
> failures list. Is there also some convenient way of finding out which GPUs are
> affected?

You can look at the log in the beginning of webgl_conformance tests, and you
will find GPU information.  However, it may still break GPU waterfall as we have
more varieties of OS/GPU on the waterfall, which aren't covered by try bots.  So
when this lands, probably you need to look at the gpu waterfall
(http://build.chromium.org/p/chromium.gpu/console) and land new entries in the
webgl_conformance_expectations.py file accordingly.

[oetuaho-nv, 2014-08-01 09:17:03]

Patch set 3 addresses the review comments. I'll keep an eye on the GPU bots
after it's merged.

[oetuaho-nv, 2014-08-05 09:22:15]

Zhenyao, could you review the updated patch?

[Zhenyao Mo, 2014-08-06 19:02:40]

LGTM

Thank you.

[oetuaho-nv, 2014-08-07 07:46:18]

The CQ bit was checked by oetuaho@nvidia.com

[commit-bot: I haz the power, 2014-08-07 07:48:28]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/oetuaho@nvidia.com/419033012/40001

[commit-bot: I haz the power, 2014-08-07 10:43:45]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[commit-bot: I haz the power, 2014-08-07 10:47:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-08-07 10:47:07]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[oetuaho-nv, 2014-08-07 11:14:49]

The CQ bit was unchecked by oetuaho@nvidia.com

[oetuaho-nv, 2014-08-07 11:14:51]

The CQ bit was checked by oetuaho@nvidia.com

[commit-bot: I haz the power, 2014-08-07 11:16:12]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/oetuaho@nvidia.com/419033012/60001

[commit-bot: I haz the power, 2014-08-07 15:53:20]

Change committed as 288055