Issue metadata
Sign in to add a comment
|
43.1%-686.6% regression in page_cycler_v2.intl_ja_zh at 433544:434574 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8994460983789993120
,
Dec 1 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@433543 22.1825 66.5871 27 good chromium@434574 18.9899 14.3422 27 bad Bisect job ran on: linux_perf_bisect Bug ID: 670320 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.amazon.co.jp page_cycler_v2.intl_ja_zh Test Metric: timeToFirstContentfulPaint_avg/pcv1-cold/http___www.amazon.co.jp Relative Change: None Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6865 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994460983789993120 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5305371923578880 | 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 13 2016
All of the tests have either recovered or were already at previous levels. Closing.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982620331440082320 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by lanwei@chromium.org
, Dec 1 2016