New issue
Advanced search Search tips

Issue 681827 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.1% regression in performance_browser_tests at 443234:443321

Project Member Reported by rmcilroy@chromium.org, Jan 17 2017

Issue description

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

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


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

chromium-rel-win7-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 18 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: win_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : TabCapturePerformance_comp_gpu_novsync/CaptureSucceeded
  Change       : 2.31% | 34.3380743333 -> 33.5462895

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/2bbd7cf1b775e07dc16f68a18386359cfc692c23..525d6e76600f29e2f724f29584129fec46236641


Revision             Result                   N
chromium@443233      34.3381 +- 0.402113      6        good
chromium@443277      34.0167 +- 0.211277      6        good
chromium@443288      33.9346 +- 0.264315      14       good
chromium@443289      ---                      ---      build failure
chromium@443290      ---                      ---      build failure
chromium@443291      34.1283 +- 2.4872        14       bad
chromium@443294      33.8832 +- 0.758923      21       bad
chromium@443299      33.83 +- 0.483663        14       bad
chromium@443321      33.5463 +- 0.17173       6        bad

To Run This Test
  .\src\out\Release\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


| 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!
Status: WontFix (was: Untriaged)
Recovered.

Sign in to add a comment