Issue metadata
Sign in to add a comment
|
3.9%-6% regression in speedometer at 415884:415937 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 6 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9002282531438627088
,
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@415912 398.669 13.3777 18 good chromium@415916 398.246 11.6511 18 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 644195 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer Test Metric: VanillaJS-TodoMVC/VanillaJS-TodoMVC Relative Change: 0.34% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/773 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002282531438627088 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5822546740510720 | 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