Disable flaky tests on Linux Release (AMD) GPU FYI

Disable flaky tests on Linux Release (AMD) GPU FYI

Disables several flaky tests which cause Linux Release (AMD) GPU FYI
to occasionally fail. These tests are not disabled on other bots, and each case has a
bug filed for it.

Disabled test cases:
ContextLost.WebGLContextLostFromGPUProcessExit
WebglConformance.conformance_textures_texture_size_cube_maps
WebglConformance.conformance_textures_texture_mips
WebglConformance.conformance_glsl_misc_shaders_with_invariance

BUG=479975, 479983, 479981, 479952
Committed: https://crrev.com/29f2a0621c72c78b0f44b4d19a6ddd3c90fc8911
Cr-Commit-Position: refs/heads/master@{#326670}

[ericrk, 2015-04-22 22:18:17]

ericrk@chromium.org changed reviewers:
+ jmadill@chromium.org, kbr@chromium.org

[ericrk, 2015-04-22 22:21:39]

Is there an easy way to try this change out before submission?

[Jamie Madill, 2015-04-23 12:29:27]

Looks good (not an owner)

https://codereview.chromium.org/1099453004/diff/1/content/test/gpu/gpu_tests/...
File content/test/gpu/gpu_tests/context_lost_expectations.py (right):

https://codereview.chromium.org/1099453004/diff/1/content/test/gpu/gpu_tests/...
content/test/gpu/gpu_tests/context_lost_expectations.py:13: ['linux', ('amd',
0x6779)], bug=479975)
you might want to leave the sample usage in, so people don't have to edit it
back if they remove this failure expectation

[Jamie Madill, 2015-04-23 12:29:50]

Also, I don't know of any way to test without submitting as AMD isn't on the try
bots.

[Ken Russell (switch to Gerrit), 2015-04-23 17:44:58]

Yes, unfortunately there's no way to try this change on the AMD bot. However,
the CQ will at least make sure the test expectations changes are syntactically
correct.

LGTM with one minor issue addressed.

https://codereview.chromium.org/1099453004/diff/1/content/test/gpu/gpu_tests/...
File content/test/gpu/gpu_tests/context_lost_expectations.py (right):

https://codereview.chromium.org/1099453004/diff/1/content/test/gpu/gpu_tests/...
content/test/gpu/gpu_tests/context_lost_expectations.py:13: ['linux', ('amd',
0x6779)], bug=479975)
On 2015/04/23 12:29:27, Jamie Madill wrote:
> you might want to leave the sample usage in, so people don't have to edit it
> back if they remove this failure expectation

Agreed; please leave the sample usage in.

[ericrk, 2015-04-23 20:10:39]

The CQ bit was checked by ericrk@chromium.org

[ericrk, 2015-04-23 20:10:39]

The patchset sent to the CQ was uploaded after l-g-t-m from kbr@chromium.org
Link to the patchset: https://codereview.chromium.org/1099453004/#ps20001
(title: "Re-add "sample usage"")

[commit-bot: I haz the power, 2015-04-23 20:11:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1099453004/20001

[ericrk, 2015-04-23 20:12:09]

Sounds good, sample usage re-added. Submitting now - will follow up and make
sure this makes the bot go green.

https://codereview.chromium.org/1099453004/diff/1/content/test/gpu/gpu_tests/...
File content/test/gpu/gpu_tests/context_lost_expectations.py (right):

https://codereview.chromium.org/1099453004/diff/1/content/test/gpu/gpu_tests/...
content/test/gpu/gpu_tests/context_lost_expectations.py:13: ['linux', ('amd',
0x6779)], bug=479975)
On 2015/04/23 17:44:58, Ken Russell wrote:
> On 2015/04/23 12:29:27, Jamie Madill wrote:
> > you might want to leave the sample usage in, so people don't have to edit it
> > back if they remove this failure expectation
> 
> Agreed; please leave the sample usage in.

Done.

[commit-bot: I haz the power, 2015-04-23 22:15:39]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-04-23 22:17:01]

Patchset 2 (id:??) landed as
https://crrev.com/29f2a0621c72c78b0f44b4d19a6ddd3c90fc8911
Cr-Commit-Position: refs/heads/master@{#326670}