Issue metadata
Sign in to add a comment
|
10.3%-15.8% regression in blink_perf.shadow_dom at 392255:392263 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 20 2016
Kicked off a bisect in https://chromeperf.appspot.com/buildbucket_job_status/9012110651051841472
,
May 20 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@392257 24.7857 0.138172 18 good chromium@392262 25.149 1.04747 18 bad Bisect job ran on: win_perf_bisect Bug ID: 610241 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.shadow_dom Test Metric: ShadowReprojection/ShadowReprojection Relative Change: 4.35% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6529 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9012110651051841472 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5868897144668160 | 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 26 2016
This has recovered, closing. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, May 9 2016