New issue
Advanced search Search tips

Issue 784855 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
tdres...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.9% regression in speedometer at 515943:515992

Project Member Reported by tdres...@chromium.org, Nov 14 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 

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

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


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

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 


=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total

Revision             Result                  N
chromium@515942      35994.4 +- 1048.16      21      good
chromium@515967      35886.2 +- 803.588      21      unknown
chromium@515992      35821.8 +- 1008.88      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/8962941107488966080


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 


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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total

Revision             Result                  N
chromium@515942      35890.7 +- 885.238      21      good
chromium@515992      35810.8 +- 1025.26      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/8962922360279265376


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Nov 15 2017 


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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total

Revision             Result                  N
chromium@515942      35930.2 +- 913.228      21      good
chromium@515992      35866.0 +- 864.913      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/8962855232223450032


For feedback, file a bug with component Speed>Bisection

Comment 8 by sullivan@chromium.org, Jan 12 2018

Status: WontFix (was: Untriaged)
Recovered.
►

Sign in to add a comment