Issue metadata
Sign in to add a comment
|
28.4% regression in blink_perf.layout at 462284:462463 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981887904388859968
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981704982967485984
,
Apr 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981432672231116896
,
Apr 25 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 : blink_perf.layout Metric : attach-inlines/attach-inlines 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.layout Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981432672231116896 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5857901941358592 | 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 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980663208985594736
,
May 5 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: TIMEOUT The bisect was able to narrow the range, you can try running with: good_revision: cbedd2c1d97e2e45e3d476048533595763d223b3 bad_revision : 201919d8a8f8351eb79f914d6b88dd0be7cc8821 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : blink_perf.layout Metric : attach-inlines/attach-inlines Change : 3.19% | 18.3876124402 -> 18.9735566056 Revision Result N chromium@462283 18.3876 +- 0.372525 6 good chromium@462295 19.0231 +- 0.627817 6 bad chromium@462306 19.1438 +- 0.304292 6 bad chromium@462328 19.1148 +- 0.709068 6 bad chromium@462373 18.8295 +- 0.342579 6 bad chromium@462463 18.9736 +- 0.557805 5 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.layout Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980663208985594736 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5857901941358592 | 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 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 alexclarke@chromium.org
, Apr 19 2017