Issue metadata
Sign in to add a comment
|
3.1%-8.8% regression in speedometer at 403619:403630 |
||||||||||||||||||
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@403624 439.255 21.0752 12 good chromium@403627 443.266 24.5773 12 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 625635 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests speedometer Test Metric: FlightJS-TodoMVC/FlightJS-TodoMVC Relative Change: 1.29% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/617 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008061758609637232 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5782302831935488 | 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