Issue metadata
Sign in to add a comment
|
3.1%-100.4% regression in speedometer at 459665:460329 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983711166477930384
,
Mar 30 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_retina_perf_bisect Benchmark : v8.runtimestats.browsing_desktop_classic Metric : Optimize:duration_avg/browse_news/browse_news_cnn Revision Result N chromium@459783 237.561 +- 17.5058 2 good chromium@459889 251.147 +- 12.6902 3 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 --story-filter=browse.news.cnn v8.runtimestats.browsing_desktop_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983711166477930384 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5880477350625280 | 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!
,
Mar 30 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tebbi@chromium.org
, Mar 30 2017