Issue metadata
Sign in to add a comment
|
37.3%-61.2% regression in v8.runtimestats.browsing_mobile at 457156:457235 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8984909558445939360
,
Mar 17 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile Metric : API:duration_avg/browse_news/browse_news_cnn Revision Result N chromium@457155 2606.83 +- 1038.63 21 good chromium@457235 2635.12 +- 642.36 21 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 --story-filter=browse.news.cnn v8.runtimestats.browsing_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8984909558445939360 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5266178026504192 | 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 22 2017
All recovered.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982632281216849088 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bmeurer@google.com
, Mar 17 2017