Issue metadata
Sign in to add a comment
|
3.2%-3.3% regression in speedometer at 418488:418541 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 15 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001470213908711456
,
Sep 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 Std Dev N Good? chromium@418535 8404.94 158.08 18 good chromium@418536 8427.82 142.368 18 bad Bisect job ran on: android_one_perf_bisect Bug ID: 647154 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests speedometer Test Metric: EmberJS-TodoMVC/EmberJS-TodoMVC Relative Change: 2.05% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1619 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001470213908711456 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5336697305300992 | 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 15 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by nikolaos@chromium.org
, Sep 15 2016