Issue metadata
Sign in to add a comment
|
28.8%-33.2% regression in v8.browsing_desktop_ignition at 418873:418987 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 27 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000367414502183744
,
Sep 27 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@418940 290.32 19.952 18 good chromium@418941 286.037 19.2168 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 650616 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_desktop_ignition Test Metric: v8-gc-incremental-step_sum/v8-gc-incremental-step_sum Relative Change: 4.37% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1693 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000367414502183744 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5868257649623040 | 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 28 2016
Flaky metric |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by hpayer@chromium.org
, Sep 27 2016