Issue metadata
Sign in to add a comment
|
80.4% regression in v8.browsing_mobile at 468723:468785 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980401030967400288
,
May 7 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980216757452530016
,
May 8 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : v8.browsing_mobile Metric : v8-gc-scavenger_sum/browse_news/browse_news_cnn To Run This Test src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn v8.browsing_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980216757452530016 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6432920165679104 | 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 12 2017
,
Jul 18 2017
,
Jul 24 2017
The graphs recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ulan@google.com
, May 5 2017