gpu: check GL_RGB565 work in ES3 context

gpu: check GL_RGB565 work in ES3 context

BUG=535198
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

[dshwang, 2016-10-17 15:18:35]

Description was changed from

==========
gpu: check GL_RGB565 work in ES3 context

BUG=535198
==========

to

==========
gpu: check GL_RGB565 work in ES3 context

BUG=535198
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
==========

[inactive_dshwang_plz_cc_intel, 2016-10-17 15:19:03]

The CQ bit was checked by dongseong.hwang@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-17 15:19:17]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[dshwang, 2016-10-17 15:20:21]

dongseong.hwang@intel.com changed reviewers:
+ zmo@chromium.org
- dongseong.hwang@chromium.org

[dshwang, 2016-10-17 15:20:22]

https://codereview.chromium.org/2117183006/ reduced test coverage, so this CL
recover the test coverage.

Zhenyao, it requires additional testing code in production code. do you think
it's worth to add or just rely on webgl2 conformance test?

[commit-bot: I haz the power, 2016-10-17 15:21:36]

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

[commit-bot: I haz the power, 2016-10-17 15:21:37]

Dry run: Try jobs failed on following builders:
  mac_optional_gpu_tests_rel on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_optional_gpu_...)

[Zhenyao Mo, 2016-10-17 20:01:25]

On 2016/10/17 15:20:22, dshwang wrote:
> https://codereview.chromium.org/2117183006/ reduced test coverage, so this CL
> recover the test coverage.
> 
> Zhenyao, it requires additional testing code in production code. do you think
> it's worth to add or just rely on webgl2 conformance test?

Let's not worry about this.  Command buffer unit tests will soon be obsolete
when we switch to MANGLE.  Not worth your time, especially we do have coverage
of this with WebGL2 conformance tests.

[dshwang, 2016-10-18 11:32:08]

On 2016/10/17 20:01:25, Zhenyao Mo wrote:
> On 2016/10/17 15:20:22, dshwang wrote:
> > https://codereview.chromium.org/2117183006/ reduced test coverage, so this
CL
> > recover the test coverage.
> > 
> > Zhenyao, it requires additional testing code in production code. do you
think
> > it's worth to add or just rely on webgl2 conformance test?
> 
> Let's not worry about this.  Command buffer unit tests will soon be obsolete
> when we switch to MANGLE.  Not worth your time, especially we do have coverage
> of this with WebGL2 conformance tests.

got it. let me abandon it.

[dshwang, 2016-10-18 11:32:15]

Description was changed from

==========
gpu: check GL_RGB565 work in ES3 context

BUG=535198
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
==========

to

==========
gpu: check GL_RGB565 work in ES3 context

BUG=535198
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
==========