Issue metadata
Sign in to add a comment
|
3.6%-7.6% regression in speedometer at 402770:402786 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 4 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@402777 965.815 38.2324 18 good chromium@402784 946.677 33.4835 18 bad Bisect job ran on: android_s5_perf_bisect Bug ID: 625637 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer Test Metric: FlightJS-TodoMVC/FlightJS-TodoMVC Relative Change: 1.40% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/764 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008061647569869904 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5321416468070400 | 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!
,
Jul 5 2016
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by nikolaos@chromium.org
, Jul 4 2016