Issue metadata
Sign in to add a comment
|
1.7% regression in v8.infinite_scroll_tbmv2 at 459529:459612 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8983134769279677360
,
Apr 5 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : v8.infinite_scroll_tbmv2 Metric : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/flickr Revision Result N chromium@459528 2090436 +- 68.9707 21 good chromium@459612 2090442 +- 46.9813 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=flickr v8.infinite_scroll_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983134769279677360 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6463624723300352 | 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 10 2017
Most of these bugs re v8.infinite_scroll_tbmv2 should be handled through Issue 724262 .
,
Jul 11 2017
,
Jul 24 2017
Bisect bot cannot reproduce the regression. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by pmeenan@chromium.org
, Apr 5 2017