Issue metadata
Sign in to add a comment
|
37% regression in v8.google at 448960:449028 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988142139140623072
,
Feb 9 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: mac_10_11_perf_bisect Benchmark : v8.google Metric : v8_execution_cpu_total_avg/v8_execution_cpu_total_avg Change : 4.33% | 17.6810682295 -> 16.9154059481 Suspected Commit Range 5 commits in range https://chromium.googlesource.com/chromium/src/+log/804e1f6bf3075c200aebb5489ea7cb8b25b5275a..2f2c3c5ec87aee2a3e24b12c82a0a235a086c042 Revision Result N chromium@448959 17.6811 +- 2.15379 14 good chromium@448994 17.7096 +- 1.17716 14 good chromium@449006 17.5385 +- 1.9802 14 good chromium@449007 --- --- build failure chromium@449008 --- --- build failure chromium@449009 --- --- build failure chromium@449010 --- --- build failure chromium@449011 17.2181 +- 1.70652 14 bad chromium@449028 16.9154 +- 2.04273 9 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 v8.google Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988142139140623072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5900538631159808 | 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!
,
Feb 10 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tebbi@chromium.org
, Feb 9 2017