Suppress More Win/AMD WebGL failures.

It seems new drivers have a regression with 3D textures.
A few 3D texture tests were missed in the last CL.

Bug: angleproject:2424
Tbr: kbr@chromium.org
No-try: True
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I464924ae2a409d7fd1941e0ee4c9497cfa053e52
Reviewed-on: https://chromium-review.googlesource.com/975922Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#545095}

content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

@@ -236,6 +236,8 @@ class WebGL2ConformanceExpectations(WebGLConformanceExpectations):
     # Recent AMD drivers seem to have a regression with 3D textures.
     self.Fail('conformance2/textures/canvas_sub_rectangle/tex-3d-*',
         ['win', 'amd', 'd3d11'], bug=2424) # ANGLE bug ID
+    self.Fail('conformance2/textures/image/tex-3d-*',
+        ['win', 'amd', 'd3d11'], bug=2424) # ANGLE bug ID
     self.Fail('conformance2/textures/image_data/tex-3d-*',
         ['win', 'amd', 'd3d11'], bug=2424) # ANGLE bug ID
     self.Fail('conformance2/textures/misc/tex-unpack-params.html',
@@ -249,9 +251,15 @@ class WebGL2ConformanceExpectations(WebGLConformanceExpectations):
     self.Fail('deqp/functional/gles3/texturespecification/' +
         'basic_teximage3d_3d_*',
         ['win', 'amd', 'd3d11'], bug=2424) # ANGLE bug ID
+    self.Fail('deqp/functional/gles3/texturespecification/' +
+        'basic_texsubimage3d_*',
+        ['win', 'amd', 'd3d11'], bug=2424) # ANGLE bug ID
     self.Fail('deqp/functional/gles3/texturespecification/' +
         'teximage3d_pbo_3d*',
         ['win', 'amd', 'd3d11'], bug=2424) # ANGLE bug ID
+    self.Fail('deqp/functional/gles3/texturespecification/' +
+        'texsubimage3d_unpack_params.html',
+        ['win', 'amd', 'd3d11'], bug=2424) # ANGLE bug ID
 
     # Have seen this time out. Think it may be because it's currently
     # the first test that runs in the shard, and the browser might not