New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 666898 link

Starred by 2 users
Status: Fixed
Owner:
kouhei@chromium.org
Closed: Jul 2017
Cc:
█ nednguyen@chromium.org
█ benhenry@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

page_cycler_v2.intl_ja_zh failing on some Android bots

Project Member Reported by charliea@chromium.org, Nov 18 2016 
Revision range first seen: Unknown (before 10/20)

Link to failing step log: https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus9_Perf__2_%2F3391%2F%2B%2Frecipes%2Fsteps%2Fpage_cycler_v2.intl_ja_zh%2F0%2Fstdout#

The following call stack definitely seems to indicate that the test is crashing:

Traceback (most recent call last):
  _RunStoryAndProcessErrorIfNeeded at /b/rr/tmpTFRA5t/w/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:108
    test.DidRunStory(state.platform)
  DidRunStory at /b/rr/tmpTFRA5t/w/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:309
    platform.tracing_controller.StopTracing()
  StopTracing at /b/rr/tmpTFRA5t/w/src/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:47
    return self._tracing_controller_backend.StopTracing()
  StopTracing at /b/rr/tmpTFRA5t/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:108
    self._IssueClockSyncMarker()
  _IssueClockSyncMarker at /b/rr/tmpTFRA5t/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:203
    self._RecordIssuerClockSyncMarker)
  RecordClockSyncMarker at /b/rr/tmpTFRA5t/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:193
    sync_id, record_controller_clock_sync_marker_callback)
  _RecordClockSyncMarkerAsyncEvent at /b/rr/tmpTFRA5t/w/src/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:170
    'Failed to issue clock sync to devtools client')
ChromeClockSyncError: Failed to issue clock sync to devtools client

I'm going to go ahead and disable the benchmark on Android for now.

Comment 1 by charliea@chromium.org, Nov 18 2016 

Should have mentioned: this is at least failing on Nexus 5, Nexus 7v2 and Nexus 9.

Comment 2 by charliea@chromium.org, Nov 18 2016 

Some of the sites that are failing: 

  - http://goo.ne.jp/, http://hatena.ne.jp/  (Nexus 5)
  - http://goo.ne.jp/ (Nexus 7v2)
  - http://fc2.com/ja/, http://www.google.com.hk/#q=%E9%82%84%E6%8F%90%E4%BE%9B&fp=c44d333e710cb480 (on separate runs, Nexus 9)

kouhei@, can you investigate?
Project Member

Comment 3 by bugdroid1@chromium.org, Nov 20 2016 

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

commit 2d697c84620901a3e362818cd76d54ed71962bb5
Author: charliea <charliea@chromium.org>
Date: Sun Nov 20 01:15:05 2016

Disable page_cycler_v2.intl_ja_zh on Android

Various pages are failing on at least half of the Android bots.

TBR=nednguyen,kouhei
BUG= 666898 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

Review-Url: https://codereview.chromium.org/2513123003
Cr-Commit-Position: refs/heads/master@{#433439}

[modify] https://crrev.com/2d697c84620901a3e362818cd76d54ed71962bb5/tools/perf/benchmarks/page_cycler_v2.py

Comment 4 by sullivan@chromium.org, Nov 28 2016

Cc: benhenry@chromium.org
 Issue 669200  has been merged into this issue.

Comment 5 by sullivan@chromium.org, Nov 29 2016 

 Issue 669284  has been merged into this issue.

Comment 6 by kouhei@chromium.org, Jul 4 2017

Status: Fixed (was: Assigned)
pcv2 is now only for cros
►

Sign in to add a comment