Issue metadata
Sign in to add a comment
|
GPU tests fail on Nexus 5 GPU.FYI bot |
||||||||||||||||||||||
Issue descriptionhttps://ci.chromium.org/buildbot/chromium.gpu.fyi/Android%20Release%20%28Nexus%205%29/8907 https://ci.chromium.org/buildbot/chromium.gpu.fyi/Android%20Release%20%28Nexus%205%29/8908 Traceback (most recent call last): _RunGpuTest at content/test/gpu/gpu_tests/gpu_integration_test.py:132 self.RunActualGpuTest(url, *args) RunActualGpuTest at content/test/gpu/gpu_tests/context_lost_integration_test.py:90 getattr(self, test_name)(test_path) _ContextLost_WebGLContextLostFromLoseContextExtension at content/test/gpu/gpu_tests/context_lost_integration_test.py:227 'window.domAutomationController._finished') traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52 return func(*args, **kwargs) WaitForJavaScriptCondition at third_party/catapult/telemetry/telemetry/internal/actions/action_runner.py:261 return self._tab.WaitForJavaScriptCondition(*args, **kwargs) traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52 return func(*args, **kwargs) WaitForJavaScriptCondition at third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py:239 return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs) traced_function at third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52 return func(*args, **kwargs) WaitForJavaScriptCondition at third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:302 e.message + '\n' + debug_message) TimeoutException: Timed out while waiting 60s for IsJavaScriptExpressionTrue. Console output: (log) :217: Harness injected. Locals: IsJavaScriptExpressionTrue : <function IsJavaScriptExpressionTrue at 0x7f39d6d61500> condition : 'window.domAutomationController._finished' context_id : None debug_message : u'Console output:\n(log) :217: Harness injected.\n' e : TimeoutException('Timed out while waiting 60s for IsJavaScriptExpressionTrue.',) kwargs : {} timeout : 60
,
Jan 24 2018
Could this be the DevTools change 59ae56fddd4f7b232ac327e86b8c333bd165bde3 , in the blamelist? The tests report: Still showing a Error dialog for org.chromium.chrome
,
Jan 24 2018
This is very unlikely. It's a super safe change. It could potentially affect couple devtools tests, otherwise the code is not executed.
,
Jan 24 2018
Suddenly passed in https://ci.chromium.org/buildbot/chromium.gpu.fyi/Android%20Release%20%28Nexus%205%29/8915. Will monitor for a while and close as Won't Fix if it stays green.
,
Jan 24 2018
That's somewhat of a relief but also a concern since we don't know what happened. There was a V8 roll in there; could it be related? Any other suspects from the blamelist which made things start working again?
,
Jan 24 2018
No, didn't see anything suspicious in either of the blamelists. Maybe it was something infra-side? To bad we don't have infra blamelist.
,
Jan 25 2018
The first failing build contains: r2adea4d74c2e7cee0228ac74b313ed8b2c6ad61b The first passing build contains its revert: rbdba2dd2bd4120529c5285d760baff83db9985dd Given the revert's commit msg, this can prob be duped into bug 805437.
,
Jan 25 2018
,
Jan 25 2018
Thank you Ben! I wonder why there were no crashes in the logs, like the one observed in issue 805437. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ynovikov@chromium.org
, Jan 24 2018