New issue
Advanced search Search tips

Issue 770525 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Oct 2017
Cc:
shend@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

40.6% regression in system_health.common_mobile at 503198:505024

Project Member Reported by shend@chromium.org, Oct 1 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 1 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=770525

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=d0e40659becf476fe74557f3aadb0fea2e937435c1b493b3786bd160515f529d


Bot(s) for this bug's original alert(s):

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 1 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.common_mobile
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                  N
chromium@503197      2.1628 +- 5.79225       21      good
chromium@505024      5.19087 +- 24.4986      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.common_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966960727819927936


For feedback, file a bug with component Speed>Bisection

Comment 4 by shend@chromium.org, Oct 1 2017

Status: Fixed (was: Untriaged)

Comment 5 by benhenry@google.com, Jan 16

Components: Test>Telemetry

Comment 6 by benhenry@google.com, Jan 16

Components: -Speed>Telemetry
►

Sign in to add a comment