New issue
Advanced search Search tips

Issue 791474 link

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



Sign in to add a comment

3.3%-3.9% regression in speedometer at 520112:520232

Project Member Reported by hablich@chromium.org, Dec 4 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Dec 4 2017 

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

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


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

android-nexus5
android-nexus7v2
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 4 2017 


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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : speedometer
  Metric       : EmberJS-TodoMVC/EmberJS-TodoMVC

Revision             Result                  N
chromium@520150      6984.21 +- 381.188      21      good
chromium@520232      6955.54 +- 373.314      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by hablich@chromium.org, Dec 4 2017

Status: WontFix (was: Untriaged)
►

Sign in to add a comment