Issue metadata
Sign in to add a comment
|
35.3%-50.9% regression in v8.browsing_desktop_ignition at 418785:418865 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 19 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001104910505834592
,
Sep 19 2016
,
Sep 19 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@418827 0.260559 0.0130906 18 good chromium@418829 0.252241 0.0141366 18 bad Bisect job ran on: win_x64_perf_bisect Bug ID: 648171 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_desktop_ignition Test Metric: v8-gc-incremental-step_avg/v8-gc-incremental-step_avg Relative Change: 2.74% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1474 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001104910505834592 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6099538459230208 | 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 20 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ulan@google.com
, Sep 19 2016