Issue metadata
Sign in to add a comment
|
16%-23.6% regression in blink_perf.shadow_dom at 471200:471297 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8979425776096090864
,
May 16 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: mac_retina_perf_bisect Benchmark : blink_perf.shadow_dom Metric : SmallDistributionWithLayout/SmallDistributionWithLayout Revision Result N chromium@471248 17.1184 +- 1.98951 21 good chromium@471250 16.9887 +- 1.86831 21 unknown chromium@471252 16.6744 +- 1.84367 21 bad chromium@471255 16.5799 +- 1.68008 14 bad chromium@471261 16.488 +- 0.661098 6 bad chromium@471273 16.4879 +- 0.854318 9 bad chromium@471297 16.715 +- 1.20346 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.shadow_dom Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8979425776096090864 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5001366696624128 | 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 lanwei@chromium.org
, May 16 2017