New issue
Advanced search Search tips

Issue 685155 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Jan 2017
Cc:
danno@google.com
hablich@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

10.8% regression in speedometer at 445254:445603

Project Member Reported by danno@google.com, Jan 25 2017 
Dramatic regression in React on or about Jan 21.

Comment 1 by danno@google.com, Jan 25 2017 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg0O2_pgkM


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

linux-release
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 26 2017 


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@445253      716.543 +- 30.8752      14      good
chromium@445603      791.098 +- 30.2911      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8989492685391122224

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4927987595608064


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jan 26 2017 


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@445253      792.385 +- 40.5527      14      good
chromium@445603      867.872 +- 38.0693      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8989492528707011152

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5342011973959680


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jan 26 2017 


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

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@445253      720.641 +- 37.1899      14      good
chromium@445603      788.792 +- 23.0631      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8989492668367487232

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5905428736638976


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Comment 8 by hablich@chromium.org, Jan 30 2017

Cc: hablich@chromium.org
Labels: -Pri-2 ReleaseBlock-Beta Pri-1

Comment 9 by hablich@chromium.org, Jan 30 2017

Mergedinto: 684428
Status: Duplicate (was: Untriaged)
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Mar 23 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@445253      720.519 +- 27.0756      14      good
chromium@445603      792.498 +- 29.8094      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8984378612082729344

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4927987595608064


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Mar 31 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@445253      788.164 +- 28.9474      14      good
chromium@445603      868.439 +- 30.2666      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8983687325511731264

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4927987595608064


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Project Member

Comment 15 by 42576172...@developer.gserviceaccount.com, Apr 8 2017 


=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : speedometer
  Metric       : React-TodoMVC/React-TodoMVC

Revision             Result                  N
chromium@445253      720.775 +- 41.0098      14      good
chromium@445603      793.166 +- 23.7618      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests speedometer

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982961961309549392

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4927987595608064


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
►

Sign in to add a comment