Issue metadata
Sign in to add a comment
|
4.1% regression in speedometer at 416426:416448 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9002282145842793216
,
Sep 6 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@416425 936.854 23.1259 18 good chromium@416448 930.53 18.6812 18 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 644201 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer Test Metric: VanillaJS-TodoMVC/VanillaJS-TodoMVC Relative Change: 0.72% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/649 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002282145842793216 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5874679858855936 | 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!
,
Sep 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9002275246412650512
,
Sep 6 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@416337 937.049 20.907 18 good chromium@416464 927.773 17.7339 18 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 644201 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer Test Metric: VanillaJS-TodoMVC/VanillaJS-TodoMVC Relative Change: 2.25% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/650 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002275246412650512 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5802100817133568 | 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!
,
Sep 6 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by nikolaos@chromium.org
, Sep 6 2016