Issue metadata
Sign in to add a comment
|
2.9% regression in smoothness.gpu_rasterization.polymer at 380879:380890 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 15 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 Value Std. Dev. Num Values Good? chromium@380878 23.137251 0.215002 15 good chromium@380890 23.14892 0.180816 19 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 595051 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.gpu_rasterization.polymer Test Metric: frame_times/frame_times Relative Change: 1.00% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3498 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9018101469902341696 | 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 label Cr-Tests-AutoBisect. Thank you!
,
Mar 22 2016
re-kicked bisect with modified range.
,
Mar 22 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 Value Std. Dev. Num Values Good? chromium@380860 22.873604 0.249825 21 good chromium@380899 22.89368 0.281889 14 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 595051 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --also-run-disabled-tests smoothness.gpu_rasterization.polymer Test Metric: frame_times/frame_times Relative Change: 0.33% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3513 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9017517759802610000 | 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 label Cr-Tests-AutoBisect. Thank you!
,
Mar 29 2016
The ref build jumped with the ToT. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pras...@chromium.org
, Mar 15 2016