Issue metadata
Sign in to add a comment
|
57.5% regression in blink_perf.parser at 468723:468785 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980437678905429280
,
May 5 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980437666036919584
,
May 6 2017
=== Auto-CCing suspected CL author jinho.bang@samsung.com === Hi jinho.bang@samsung.com, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : jinho.bang Commit : 09c61ecc5adf140aa7a59aef0ecacc510e0be1d8 Date : Tue May 02 19:44:55 2017 Subject: PaymentHandler: Implement PaymentInstruments.keys(). Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : blink_perf.parser Metric : query-selector-last/query-selector-last Change : 0.82% | 231.644298999 -> 233.537766835 Revision Result N chromium@468722 231.644 +- 3.87768 14 good chromium@468738 224.682 +- 9.19456 6 good chromium@468746 221.032 +- 2.24029 6 good chromium@468747 246.817 +- 3.71472 6 bad <-- chromium@468748 245.81 +- 5.12019 6 bad chromium@468750 245.83 +- 3.13245 6 bad chromium@468754 246.751 +- 6.01289 6 bad chromium@468785 233.538 +- 3.61951 9 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.parser Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980437678905429280 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5796534324559872 | 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 6 2017
=== Auto-CCing suspected CL author erg@chromium.org === Hi erg@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : erg Commit : 76d6d9c5e3be62df7beb5f047e26b292997904de Date : Tue May 02 18:54:51 2017 Subject: Remove BitmapArray. Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : blink_perf.parser Metric : query-selector-last/query-selector-last Change : 1.77% | 244.795014849 -> 240.464237855 Revision Result N chromium@468722 244.795 +- 9.73018 14 good chromium@468724 242.909 +- 13.2795 9 good chromium@468725 99.721 +- 1.59655 6 bad <-- chromium@468726 190.624 +- 194.472 9 bad chromium@468730 236.748 +- 2.10668 6 bad chromium@468738 229.244 +- 1.23533 6 bad chromium@468754 240.726 +- 3.60225 9 bad chromium@468785 240.464 +- 3.00954 9 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.parser Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980437666036919584 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5773611765334016 | 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 9 2017
This is highly unlikely to be my patch which should be a no-op; //skia/public/interfaces is not linked into blink, if i'm reading the grep of gn files correctly.
,
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 kraynov@chromium.org
, May 5 2017