Issue metadata
Sign in to add a comment
|
3.6%-40.7% regression in v8.runtimestats.browsing_mobile_classic at 475248:475536 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976807641555744832
,
Jun 15 2017
Assigning to performance sheriff.
,
Jun 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976623080747730288
,
Jun 17 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.runtimestats.browsing_mobile_classic Metric : Optimize:duration_avg/browse_media/browse_media_facebook_photos 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.media.facebook.photos v8.runtimestats.browsing_mobile_classic Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976623080747730288 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5234124823986176 | 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!
,
Jun 18 2017
Affects classic V8 configuration only. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tebbi@chromium.org
, Jun 14 2017