Telemetry fails with "Timed out while waiting 5s for py_utils.WaitFor(lambda: tab_id not in self.IterContextIds(), timeout=5)" in the log |
|||||||||||
Issue description
Chrome Version: 60.0.3088 onwards
Chrome OS Version: 9517.0 developer-build
Chrome OS Platform: All
Network info: Wired Ethernet
For the last several days - starting with CrOS version 9517.0 and Chromium 60.0.3088 - most telemetry workloads have been failing with the following in the log:
[ RUN ] http://www.fda.gov@{'cache_temperature': 'pcv1-cold'}
Traceback (most recent call last):
File "/build/chromium_build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 81, in _RunStoryAndProcessErrorIfNeeded
state.WillRunStory(story)
File "/build/chromium_build/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
return func(*args, **kwargs)
File "/build/chromium_build/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 221, in WillRunStory
self.browser.tabs[-1].Close()
File "/build/chromium_build/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 75, in traced_function
return func(*args, **kwargs)
File "/build/chromium_build/src/third_party/catapult/telemetry/telemetry/internal/browser/tab.py", line 100, in Close
self._tab_list_backend.CloseTab(self.id)
File "/build/chromium_build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/tab_list_backend.py", line 67, in CloseTab
py_utils.WaitFor(lambda: tab_id not in self.IterContextIds(), timeout=5)
File "/build/chromium_build/src/third_party/catapult/common/py_utils/py_utils/__init__.py", line 132, in WaitFor
(timeout, GetConditionString()))
TimeoutException: Timed out while waiting 5s for py_utils.WaitFor(lambda: tab_id not in self.IterContextIds(), timeout=5).
,
May 10 2017
I also meet this problem in Chrome Version: 60.0.3089.0 Platform Build Version: 9530.0.0 when running benchmark “page_cycler.V2.typical25” and "smoothness.top25"
,
May 10 2017
Ben: can you help triaging this.
,
May 10 2017
,
May 12 2017
Our internal test shows the last pass for page_cycler_v2 is around 9523.0.0, and I can reproduce the timeout on 9524.0.0.
,
May 12 2017
This should have be fixed by https://chromium.googlesource.com/chromium/src.git/+/8e75b1bc9944bfe1a4a1a006e212418243e96abd Telemetry seems to be working again on today's master.
,
Sep 12 2017
,
Sep 19 2017
This has started again from 9944.0.0, for the following tests: - telemetry_Benchmarks.page_cycler_v2.typical_25 - telemetry_Benchmakrs.smoothness.top_25_smooth - telemetry_Benchmarks.memory_desktop
,
Sep 19 2017
Is it working on other platforms apart from ChromeOS?
,
Sep 19 2017
I checked out this commit https://chromium.googlesource.com/chromium/src/+/3cd860762dd1b4b595c959c2dfff16f84fa99d3d in chrome (which is the version that ChromeOS 9944.0.0 uses) and built Chrome on my linux workstation, then run: `./run_benchmark run --browser-executable=../../out/host/default/chrome memory.desktop` It worked fine. Haven't tested other platforms.
,
Sep 20 2017
I meet this issue too when I run below command on IA device R62-9954.0.0 :
./run_benchmark --remote=10.239.115.15 --browser=cros-chrome --reset-results --output-format=html page_cycler_v2.typical_25
or
./run_benchmark --remote=10.239.115.15 --browser=cros-chrome --reset-results --output-format=html smoothness.top_25_smooth
or
./run_benchmark --remote=10.239.115.15 --browser=cros-chrome --reset-results --output-format=html --also-run-disabled-tests tab_switching.typical_25
The error is below:
[ RUN ] multitab:misc:typical24@{'case': 'multitab', 'group': 'misc'}
(WARNING) 2017-09-20 15:12:55,240 multi_tab_stories.RunNavigateSteps:37 WaitForNetworkQuiescence() timeout, url[15]: http://premierleague.com
Traceback (most recent call last):
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 105, in _RunStoryAndProcessErrorIfNeeded
state.RunStory(results)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
return func(*args, **kwargs)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 331, in RunStory
self._current_page.Run(self)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/telemetry/telemetry/page/__init__.py", line 112, in Run
self.RunPageInteractions(action_runner)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/tools/perf/page_sets/system_health/system_health_story.py", line 142, in RunPageInteractions
self._DidLoadDocument(action_runner)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/tools/perf/page_sets/system_health/multi_tab_stories.py", line 42, in _DidLoadDocument
tab.WaitForFrameToBeDisplayed()
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
return func(*args, **kwargs)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 104, in WaitForFrameToBeDisplayed
timeout=timeout)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
return func(*args, **kwargs)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/browser/web_contents.py", line 192, in WaitForJavaScriptCondition
return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py", line 52, in traced_function
return func(*args, **kwargs)
File "/home/stang23/chromeos/chromiumos-3/chrome_root/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 287, in WaitForJavaScriptCondition
e.message + '\n' + debug_message)
TimeoutException: Timed out while waiting 90s for IsJavaScriptExpressionTrue.
Console output:
[ FAILED ] multitab:misc:typical24@{'case': 'multitab', 'group': 'misc'} (202283 ms)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] multitab:misc:typical24@{'case': 'multitab', 'group': 'misc'}
1 FAILED TEST
,
Sep 20 2017
Please add jayeeta.bandyopadhyay@intel.com, lingyun.cai@intel.com, rachna.doggalli@intel.com and me into the cc list. Thanks a lot.
,
Sep 20 2017
Tested the following: - ChromeOS 9943.0.0 with Chrome 63.0.3212.0 => worked - ChromeOS 9943.0.0 with Chrome 63.0.3216.0 => not working So likely the problem is in Chrome. I'm going to bisect between 63.0.3212.0 and 63.0.3216.0.
,
Sep 22 2017
Bisecting between 63.0.3212.0 and 63.0.3216.0 narrows down to this CL: https://chromium-review.googlesource.com/639024 [DevTools] Mark targets as 'page' by default in ChromeDevToolsManagerDelegate Dmitry, any idea if this CL is related to the issue?
,
Sep 22 2017
,
Sep 25 2017
Can #763834 be made public?
,
Sep 25 2017
On R63-9971.0.0, this issue is fixed. Thanks a lot
,
Jan 16
,
Jan 16
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 Deleted