New issue
Advanced search Search tips

Issue 799439 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 799080



Sign in to add a comment

Failures on v8.browsing_mobile-future benchmark on twitter, qq pages

Project Member Reported by mythria@chromium.org, Jan 5 2018

Issue description

There are some failures on twitter, qq pages with the following stack trace: 

(INFO) 2018-01-01 16:00:45,033 webpagereplay_go_server.StartServer:230  WPR ports: {'http': 55085, 'https': 46463}
(INFO) 2018-01-01 16:00:45,034 ts_proxy_server._IssueCommand:97  Issuing command to ts_proxy_server: set mapports 443:46463,*:55085
(INFO) 2018-01-01 16:00:45,036 browser.DumpStateUponFailure:339  *************** BROWSER STANDARD OUTPUT ***************
(INFO) 2018-01-01 16:00:45,036 browser.DumpStateUponFailure:341  Cannot get standard output on Android
(INFO) 2018-01-01 16:00:45,036 browser.DumpStateUponFailure:344  *********** END OF BROWSER STANDARD OUTPUT ************
(INFO) 2018-01-01 16:00:45,037 browser.DumpStateUponFailure:346  ********************* BROWSER LOG *********************
(INFO) 2018-01-01 16:00:45,037 browser.DumpStateUponFailure:348  No log file
(INFO) 2018-01-01 16:00:45,037 browser.DumpStateUponFailure:351  ***************** END OF BROWSER LOG ******************
(INFO) 2018-01-01 16:00:45,038 cmd_helper._ValidateAndLogCommand:160  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG860442028A4GC shell '( /system/bin/screencap -p /data/local/tmp/temp_file-ec08ae4dded62.png );echo %$?'
(INFO) 2018-01-01 16:00:45,624 cmd_helper._ValidateAndLogCommand:160  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG860442028A4GC pull /data/local/tmp/temp_file-ec08ae4dded62.png /b/swarming/w/itasknq7/tmpYeb0qC.png
(INFO) 2018-01-01 16:00:45,808 cmd_helper._ValidateAndLogCommand:160  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s AG860442028A4GC shell 'rm -f /data/local/tmp/temp_file-ec08ae4dded62.png'
(WARNING) 2018-01-01 16:00:45,840 artifact_results.AddArtifact:113  Moving artifact file '/b/swarming/w/itasknq7/tmpYeb0qC.png' to '/b/swarming/w/itasknq7/tmpLV1vJCtelemetry/artifacts'
Traceback (most recent call last):
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py", line 117, in _RunStoryAndProcessErrorIfNeeded
    state.WillRunStory(story)
  File "/b/swarming/w/ir/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 "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/page/shared_page_state.py", line 235, in WillRunStory
    if len(self.browser.tabs) == 0:
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/browser/tab_list.py", line 15, in __len__
    return self._tab_list_backend.__len__()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend_list.py", line 95, in __len__
    self._Update()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend_list.py", line 99, in _Update
    backends_map = self._devtools_client.GetUpdatedInspectableContexts()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_client_backend.py", line 372, in GetUpdatedInspectableContexts
    contexts = self._ListInspectableContexts()
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_client_backend.py", line 297, in _ListInspectableContexts
    return self._devtools_http.RequestJson('')
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_http.py", line 107, in RequestJson
    return json.loads(self.Request(path, timeout))
  File "/b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_http.py", line 88, in Request
    response = self._conn.getresponse()
  File "/usr/lib/python2.7/httplib.py", line 1136, in getresponse
    response.begin()
  File "/usr/lib/python2.7/httplib.py", line 453, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.7/httplib.py", line 409, in _read_status
    line = self.fp.readline(_MAXLINE + 1)
  File "/usr/lib/python2.7/socket.py", line 480, in readline
    data = self._sock.recv(self._rbufsize)
DevToolsClientConnectionError: [Errno 104] Connection reset by peer
(INFO) 2018-01-01 16:00:45,856 exception_formatter.PrintFormattedException:19  Try printing formatted exception: None None None
Exception raised when cleaning story run: 
Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py:150
    test.DidRunStory(state.platform, results)
  DidRunStory at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:290
    trace_result, _ = platform.tracing_controller.StopTracing()
  StopTracing at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:53
    return self._tracing_controller_backend.StopTracing()
  StopTracing at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:109
    self._IssueClockSyncMarker()
  _IssueClockSyncMarker at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:215
    self._RecordIssuerClockSyncMarker)
  RecordClockSyncMarker at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:178
    raise ChromeClockSyncError('Cannot issue clock sync. No devtools clients')
ChromeClockSyncError: Cannot issue clock sync. No devtools client
 
Can you link to the bots where this is failing Mythri?
Blocking: 799080
Test results for this bot/benchmark:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=v8.browsing_mobile-future&builder=chromium.perf%3AAndroid%20One%20Perf

Looks like browse:social:facebook_infinite_scroll and browse:social:pinterest_infinite_scroll have been always failing here. I suggest disabling those and file a bug to investigate, fix them, and re-enable.

The others are more like flakes. I don't think any is particularly worrying, but let's keep a look in case the flakes remain constant.
Thanks Juan. Currently, the entire benchmark is disabled. So, I will enable the benchmark again and disable infinite_scroll stories.
Thanks Mythri!
Project Member

Comment 7 by bugdroid1@chromium.org, Jan 8 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7463caf8b95a8e1a70021aace0bab4a82f909946

commit 7463caf8b95a8e1a70021aace0bab4a82f909946
Author: Mythri Alle <mythria@chromium.org>
Date: Mon Jan 08 12:35:04 2018

Enable v8.browsing_mobile-future benchmark on Android one

Disable facebook_infinite_scroll and pinterest_infinite_scroll
that are consistently failing on android one perf bot. Enable
the v8.browsing_mobile-future on Android one.

Bug:  chromium:799439 ,  chromium:799080 
Change-Id: I72d59336c35387cba927b2ff89f38929cb2e749c
Reviewed-on: https://chromium-review.googlesource.com/852492
Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Commit-Queue: Mythri Alle <mythria@chromium.org>
Cr-Commit-Position: refs/heads/master@{#527614}
[modify] https://crrev.com/7463caf8b95a8e1a70021aace0bab4a82f909946/tools/perf/expectations.config

Status: Fixed (was: Untriaged)
I think twitter and qq are kind of stable now. Here are the results from last few runs: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=v8.browsing_mobile&builder=chromium.perf%3AAndroid%20One%20Perf.

I am marking this as fixed. We have 799080 to track the failures due to large trace size. Please feel free to reopen if required.

Sign in to add a comment