Issue metadata
Sign in to add a comment
|
5% regression in v8.runtimestats.browsing_mobile_classic at 471725:471837 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978920521207416384
,
May 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : Total:duration_avg/browse_chrome/browse_chrome_newtab Revision Result N chromium@471724 16479.4 +- 999.829 21 good chromium@471837 16334.5 +- 3669.29 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.chrome.newtab v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978920521207416384 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5315782629654528 | 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!
,
May 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978910654244277744
,
May 22 2017
,
May 22 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : Total:duration_avg/browse_chrome/browse_chrome_newtab Revision Result N chromium@471724 16335.7 +- 1721.37 21 good chromium@471781 16737.1 +- 3593.44 21 unknown chromium@471837 16613.3 +- 637.732 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.chrome.newtab v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978910654244277744 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5315782629654528 | 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! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jarin@google.com
, May 22 2017