Issue metadata
Sign in to add a comment
|
11%-11.8% regression in blink_perf.parser at 395908:395987 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 27 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@395937 4659.16 58.1745 12 good chromium@395950 4715.87 132.552 18 bad Bisect job ran on: linux_perf_bisect Bug ID: 615419 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.parser Test Metric: html-parser-threaded/html-parser-threaded Relative Change: 1.23% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6509 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011494982184269152 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5838254767603712 | 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 Tests>AutoBisect. Thank you!
,
May 27 2016
=== Auto-CCing suspected CL author wangxianzhu@chromium.org === Hi wangxianzhu@chromium.org, the bisect results pointed to your CL below as possibly causing a regression. Please have a look at this info and see whether your CL be related. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : Enable CHECK_DISPLAY_ITEM_CLIENT_ALIVENESS temporarily for debugging crbug.com/609218 Author : wangxianzhu Commit description: BUG=609218 Review-Url: https://codereview.chromium.org/2007363002 Cr-Commit-Position: refs/heads/master@{#395986} Commit : 7bd8598d9284ccd749ca0c4605714eb66da943ef Date : Wed May 25 20:57:51 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@395937 6130.33 38.6178 5 good chromium@395962 6237.85 148.705 5 good chromium@395975 6273.62 75.8048 5 good chromium@395981 6169.35 67.6803 5 good chromium@395984 6094.89 161.989 5 good chromium@395985 6299.25 99.2138 5 good chromium@395986 6845.39 75.2401 5 bad <-- chromium@395987 6889.29 82.128 5 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 615419 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.parser Test Metric: html-parser-threaded/html-parser-threaded Relative Change: 12.38% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1311 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9011484108660779072 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5900240809361408 | 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 Tests>AutoBisect. Thank you!
,
May 27 2016
This is a temporary CL causing temporary performance regressions. Will revert the CL after we address the issue under investigation.
,
May 27 2016
Sounds like this is temporary, which is good. When can we expect the revert?
,
May 27 2016
The revert will be before m-53 branch.
,
Jun 10 2016
,
Jun 28 2016
Restored. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by rsch...@chromium.org
, May 27 2016