Issue metadata
Sign in to add a comment
|
4%-4.6% regression in speedometer at 418797:418823 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 16 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001369821092301392
,
Sep 16 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@418805 170.037 19.376 18 good chromium@418811 167.691 8.2454 18 bad Bisect job ran on: winx64nvidia_perf_bisect Bug ID: 647634 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests speedometer Test Metric: VanillaJS-TodoMVC/VanillaJS-TodoMVC Relative Change: 6.88% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1869 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001369821092301392 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6074841793298432 | 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 16 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by nikolaos@chromium.org
, Sep 16 2016