Issue metadata
Sign in to add a comment
|
16.3%-112.8% regression in v8.runtimestats.browsing_mobile at 465212:466766 |
||||||||||||||||||||||
Issue descriptionAnother instance of Android phone getting hot?
,
Apr 26 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981272267222727440
,
Apr 26 2017
232 F before the alert than 277 F ... so maybe?
,
Apr 26 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : API:duration_avg/browse_news/browse_news_globo Revision Result N chromium@465530 3489.96 +- 1684.71 21 good chromium@466318 3663.85 +- 1397.43 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.globo v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981272267222727440 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5277817719226368 | 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 26 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981248861167929072
,
Apr 26 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : API:duration_avg/browse_news/browse_news_globo Revision Result N chromium@465530 3457.49 +- 1460.61 21 good chromium@466318 3634.14 +- 1462.02 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.globo v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981248861167929072 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5277817719226368 | 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 27 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981138496646880832
,
Apr 28 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : v8.runtimestats.browsing_mobile_classic Metric : GC:duration_avg/browse_news/browse_news_globo Revision Result N chromium@465530 6184.64 +- 3083.92 21 good chromium@466318 6183.43 +- 2723.23 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.globo v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981138496646880832 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5277817719226368 | 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!
,
Jul 18 2017
,
Sep 20 2017
,
Sep 20
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 22
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bmeurer@google.com
, Apr 26 2017