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

Issue 633222 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
kouhei@chromium.org
█ nednguyen@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

page_cycler.top_10_mobile failure on chromium.perf Android Nexus 5 Perf (3), Android Nexus6 Perf (3) and Android One Perf (3)

Project Member Reported by simonhatch@chromium.org, Aug 1 2016 
https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%283%29?numbuilds=200

Looks like it started around July 27




Traceback (most recent call last):
  RunBenchmark at /b/build/slave/Android_Nexus5_Perf__3_/build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:317
    benchmark.ShouldTearDownStateAfterEachStorySetRun())
  Run at /b/build/slave/Android_Nexus5_Perf__3_/build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:226
    _RunStoryAndProcessErrorIfNeeded(story, results, state, test)
  _RunStoryAndProcessErrorIfNeeded at /b/build/slave/Android_Nexus5_Perf__3_/build/src/third_party/catapult/telemetry/telemetry/internal/story_runner.py:85
    state.RunStory(results)
  RunStory at /b/build/slave/Android_Nexus5_Perf__3_/build/src/third_party/catapult/telemetry/telemetry/page/shared_page_state.py:321
    self._current_page, self._current_tab, results)
  ValidateAndMeasurePage at /b/build/slave/Android_Nexus5_Perf__3_/build/src/tools/perf/measurements/page_cycler.py:153
    self._cpu_metric.AddResults(tab, results)
  AddResults at /b/build/slave/Android_Nexus5_Perf__3_/build/src/tools/perf/metrics/cpu.py:46
    cpu_stats = _SubtractCpuStats(self._stop_cpu, self._start_cpu)
  _SubtractCpuStats at /b/build/slave/Android_Nexus5_Perf__3_/build/src/tools/perf/metrics/cpu.py:95
    'Expected total_time > 0, was: %d' % total_time)
AssertionError: Expected total_time > 0, was: 4252017639

Locals:
  cpu_process_time : 0.27
  cpu_stats        : {'Gpu': {'TotalTime': 12.34, 'CpuProcessTime': 2.65}, 'Other': {}, 'Renderer': {'TotalTime': 12.34, 'CpuProcessTime': 3.05}, 'Browser': {'TotalTime': 12.34, 'CpuProcessTime': 9.81}}
  cpu_usage        : {}
  process_type     : 'Gpu'
  start_cpu_stats  : {'Gpu': {'TotalTime': 42949669.27, 'CpuProcessTime': 2.38}, 'Other': {}, 'Renderer': {'TotalTime': 42949669.27, 'CpuProcessTime': 3.42}, 'Browser': {'TotalTime': 42949669.27, 'CpuProcessTime': 8.48}}
  total_time       : 4252017639.07
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 1 2016 

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

commit 25046e7127260c24ff0e4f442b3fac61dbffee9c
Author: simonhatch <simonhatch@chromium.org>
Date: Mon Aug 01 19:39:07 2016

Disable page_cycler.top_10_mobile on Nexus 5.

TBR=nednyugen@google.com
BUG= 633222 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;

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

[modify] https://crrev.com/25046e7127260c24ff0e4f442b3fac61dbffee9c/tools/perf/benchmarks/page_cycler.py

Comment 2 by pras...@chromium.org, Aug 2 2016

Summary: page_cycler.top_10_mobile failure on chromium.perf Android Nexus 5 Perf (3), Android Nexus6 Perf (3) and Android One Perf (3) (was: page_cycler.top_10_mobile failure on chromium.perf Android Nexus 5 Perf (3))
Also failing on Android Nexus6 Perf (3) and Android One Perf (3) perf bots.
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus6%20Perf%20%283%29/builds/2895
https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20One%20Perf%20%283%29/builds/2905

Comment 3 by nedngu...@google.com, Aug 2 2016 

Thanks for reporting this. Can you kick off a bisect?

Comment 4 by nedngu...@google.com, Aug 2 2016 

Nvm. I realized that this is an android-only page_cycler benchmark, hence we can just delete it since Kouhei already ported this to page_cycler_v2.
Project Member

Comment 5 by bugdroid1@chromium.org, Aug 2 2016 

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

commit 7604a139438e4170a2247043679c0d044232b507
Author: simonhatch <simonhatch@chromium.org>
Date: Tue Aug 02 20:10:26 2016

Remove page_cycler.top_10_mobile. Already ported to page_cycler_v2.

R=nednguyen@google.com
BUG= 633222 

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

[modify] https://crrev.com/7604a139438e4170a2247043679c0d044232b507/tools/perf/benchmarks/page_cycler.py

Comment 6 by simonhatch@chromium.org, Aug 4 2016

Status: WontFix (was: Untriaged)
Since we ended up removing the benchmark completely, gonna close this.
►

Sign in to add a comment