Issue metadata
Sign in to add a comment
|
19.4%-34.4% regression in blink_perf.bindings at 456323:456329 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8985203650617785600
,
Mar 14 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : blink_perf.bindings Metric : set-attribute-rare/set-attribute-rare Revision Result N chromium@456322 96.9694 +- 152.228 20 good chromium@456329 86.7854 +- 140.326 21 bad 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 blink_perf.bindings Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8985203650617785600 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5796344091901952 | 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 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982580649532942576
,
Jul 27 2017
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hjd@chromium.org
, Mar 13 2017