Mark all WebGL 2.0 tests flaky on Win/Intel.

content/test/gpu/gpu_tests/webgl2_conformance_expectations.py

Index: content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
diff --git a/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py b/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
index 3900acda65c0b0b40e90a91a838ffcc79a5df0df..4d196ed34eed3f834081d34a6f83fe62071a3571 100644
--- a/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
+++ b/content/test/gpu/gpu_tests/webgl2_conformance_expectations.py
@@ -162,7 +162,7 @@ class WebGL2ConformanceExpectations(WebGLConformanceExpectations):
     self.Fail('deqp/functional/gles3/transformfeedback/*.html',
         ['win', ('amd', 0x6779)], bug=483282)
 
-    # It's unfortunate that this suppression needs to be so broad, but
+    # It's unfortunate that these suppressions need to be so broad, but
     # basically any test that uses readPixels is potentially flaky, and
     # it's infeasible to suppress individual failures one by one.
     self.Flaky('conformance/*', ['win', ('amd', 0x6779)], bug=491419)
@@ -222,6 +222,13 @@ class WebGL2ConformanceExpectations(WebGLConformanceExpectations):
     self.Flaky('deqp/functional/gles3/transformfeedback/*.html',
         ['win', 'intel'], bug=626068)
 
+    # It's unfortunate that these suppressions need to be so broad, but it
+    # looks like the D3D11 device can be lost spontaneously on this
+    # configuration while running basically any test.
+    self.Flaky('conformance/*', ['win', 'intel'], bug=628395)
+    self.Flaky('conformance2/*', ['win', 'intel'], bug=628395)
+    self.Flaky('deqp/*', ['win', 'intel'], bug=628395)
+
     # Mac only.
     self.Fail('conformance/glsl/misc/shaders-with-invariance.html',
               ['mac'], bug=483282)