New issue
Advanced search Search tips

Issue 686070 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.3% regression in thread_times.key_silk_cases at 445772:445820

Project Member Reported by sullivan@chromium.org, Jan 27 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=686070

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 27 2017


=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_renderer_main_cpu_time_per_frame/thread_renderer_main_cpu_time_per_frame

Suspected Commit Range
  7 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1fc58f0e3b68581b5832176bfd922bc28ecb7b54..9686be68e53348bab6f4ce846bf07d494f1575a0


Revision             Result                   N
chromium@445771      4.84906 +- 0.167374      6        good
chromium@445772      ---                      ---      build failure
chromium@445773      ---                      ---      build failure
chromium@445774      ---                      ---      build failure
chromium@445775      ---                      ---      build failure
chromium@445776      ---                      ---      build failure
chromium@445777      ---                      ---      build failure
chromium@445778      5.23949 +- 0.177648      6        bad
chromium@445784      5.22638 +- 0.100726      6        bad
chromium@445796      5.24614 +- 0.129264      6        bad
chromium@445820      5.23485 +- 0.137919      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.key_silk_cases

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

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


| 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!
Mergedinto: 685179
Status: Duplicate (was: Untriaged)
This looks like a slimming-paint-invalidation regression.

Sign in to add a comment