Issue metadata
Sign in to add a comment
|
17.1%-39.3% regression in v8.infinite_scroll-ignition_tbmv2 at 435981:436164 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 5 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994155911416485328
,
Dec 5 2016
===== BISECT JOB RESULTS ===== Status: failed === Bisection aborted === The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence. Please contact the the team (see below) if you believe this is in error. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@436091 0.767206 0.382718 25 good chromium@436113 0.750286 0.421988 25 bad Bisect job ran on: winx64nvidia_perf_bisect Bug ID: 671070 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2 Test Metric: v8-gc-incremental-step_avg/v8-gc-incremental-step_avg Relative Change: 2.21% Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64nvidia_perf_bisect/builds/1968 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994155911416485328 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5894210664792064 | 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!
,
Dec 6 2016
Now recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by qyears...@chromium.org
, Dec 5 2016