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

Issue 732309 link

Starred by 1 user
Status: Duplicate
Merged: issue 731659
Owner: ----
Closed: Jun 2017
Cc:
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.8% regression in thread_times.tough_scrolling_cases at 477078:477224

Project Member Reported by alexclarke@chromium.org, Jun 12 2017 
See the link to graphs below.

Comment 1 by alexclarke@chromium.org, Jun 12 2017 

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

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jun 12 2017 


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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 3e863242981adb61aa416fda0607470df3ca0eb6
  bad_revision : 4b96029ded180941d12ada1e2ee5eee3340ae20a

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame

Revision             Result                   N
chromium@477077      32.1188 +- 0.448405      6      good
chromium@477151      32.1907 +- 0.390243      6      good
chromium@477188      32.0881 +- 0.340629      6      good
chromium@477197      32.075 +- 0.201472       6      good
chromium@477202      32.4069 +- 0.147312      6      bad
chromium@477206      32.5031 +- 0.15834       6      bad
chromium@477224      32.6537 +- 0.142218      6      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 thread_times.tough_scrolling_cases

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

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


| 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 6 by 42576172...@developer.gserviceaccount.com, Jun 13 2017 


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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: c2cdd438af27411be2758177914d898fc85768ef
  bad_revision : ba2889de7991c1f5162cd12dd6cc6e4de3bc3ac0

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame

Revision             Result                   N
chromium@477077      32.0264 +- 0.371643      6      good
chromium@477151      32.2649 +- 0.162944      6      good
chromium@477188      32.1906 +- 0.236223      6      good
chromium@477206      32.6269 +- 0.534448      6      bad
chromium@477224      32.6559 +- 0.359486      6      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 thread_times.tough_scrolling_cases

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

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


| 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 7 by 42576172...@developer.gserviceaccount.com, Jun 13 2017 


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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 2c5eae86eddc741f7619898863ab70d89a29f39e
  bad_revision : 54316cef205352d84ee18a4fdc67eabc5d9c7a9d

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame

Revision             Result                   N
chromium@477000      32.1719 +- 0.274022      6      good
chromium@477150      32.2119 +- 0.287645      6      good
chromium@477300      32.6607 +- 0.135458      6      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 thread_times.tough_scrolling_cases

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

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


| 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 9 by 42576172...@developer.gserviceaccount.com, Jun 13 2017 


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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 2c5eae86eddc741f7619898863ab70d89a29f39e
  bad_revision : 54316cef205352d84ee18a4fdc67eabc5d9c7a9d

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


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame

Revision             Result                   N
chromium@477000      32.1719 +- 0.274022      6      good
chromium@477150      32.2119 +- 0.287645      6      good
chromium@477300      32.6607 +- 0.135458      6      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 thread_times.tough_scrolling_cases

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

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


| 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 11 by 42576172...@developer.gserviceaccount.com, Jun 15 2017

Mergedinto: 731659
Status: Duplicate (was: Untriaged)

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : cathiechen
  Commit : 47f9b0ff7d4594f6633956ac570966439b4d5125
  Date   : Tue Jun 06 04:51:41 2017
  Subject: Fix font-size shaking issue in some page

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.tough_scrolling_cases
  Metric       : thread_total_all_cpu_time_per_frame/thread_total_all_cpu_time_per_frame
  Change       : 2.31% | 32.0705140336 -> 32.6840872493

Revision             Result                   N
chromium@477077      32.0705 +- 0.406884      8      good
chromium@477151      32.6528 +- 4.1147        9      good
chromium@477188      32.1147 +- 0.399027      9      good
chromium@477197      32.1756 +- 0.522691      9      good
chromium@477198      33.6787 +- 0.445792      6      bad       <--
chromium@477199      33.7022 +- 0.430623      6      bad
chromium@477200      33.7189 +- 0.23317       6      bad
chromium@477202      33.5419 +- 0.477367      6      bad
chromium@477206      32.6438 +- 1.14335       9      bad
chromium@477224      32.6841 +- 0.581474      9      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 thread_times.tough_scrolling_cases

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

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


| 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