Issue metadata
Sign in to add a comment
|
3.4%-19.7% regression in performance_browser_tests at 450084:450252 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987577778275585328
,
Feb 15 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: win_8_perf_bisect Benchmark : performance_browser_tests Metric : TabCapturePerformance/Capture Revision Result N chromium@450083 27.7048 +- 1.00437 21 good chromium@450252 27.624 +- 1.36355 21 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/8987577778275585328 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5029815716937728 | 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!
,
Apr 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982659694120027744
,
Jul 27 2017
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by kouhei@google.com
, Feb 15 2017