WebglConformance_deqp_functional_gles3_shaderoperator_binary_operator_nn timing out on Mac Retina Release (NVIDIA) |
|||||
Issue descriptiontwice so far, starting with: https://build.chromium.org/p/chromium.gpu.fyi/builders/Mac%20Retina%20Release%20%28NVIDIA%29/builds/5663 webgl2_conformance_tests on NVIDIA GPU on Mac Retina on Mac-10.12.6 Unexpected Failures: gpu_tests.webgl_conformance_integration_test.WebGLConformanceIntegrationTest.WebglConformance_deqp_functional_gles3_shaderoperator_binary_operator_01 (and _00) "WebglConformance_deqp_functional_gles3_shaderoperator_binary_operator_01": { "actual": "FAIL", "times": [ 321.7678 TimeoutException: Timed out while waiting 300s for IsJavaScriptExpressionTrue. No likely CLs to blame (ANGLE or V8). This test has been close to 300s in the past. Test _00 seems to average 70 seconds (based on a few builds) but went over 300 in build 5664. Do we just need a longer timeout?
,
Nov 9 2017
,
Nov 10 2017
+zmo@ for triage.
,
Feb 26 2018
GPU triage: lowering priority
,
Apr 10 2018
Got this again here https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac%20FYI%20Retina%20Release%20%28NVIDIA%29/916 Previous run in build 915 took 279.4215s
,
Apr 11 2018
In order to increase the timeout for just this one test, the test_expectations.py infrastructure in src/content/test/gpu/gpu_tests/ would have to be extended to add a new "Slow" type of expectation (probably orthogonal to the existing ones) which would record a per-test timeout. Then _GetTestTimeout in src/content/test/gpu/gpu_tests/webgl_conformance_integration_test.py would need to be revised to consult the test expectations. Alternatively, this test could be split up further since it sounds like it's often close to the 300s default timeout. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by cwallez@chromium.org
, Oct 19 2017