Issue metadata
Sign in to add a comment
|
6.5%-53.3% regression in page_cycler_v2.intl_ko_th_vi at 428963:429224 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8997022910690041520
,
Nov 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@429025 732.381 97.8275 18 good chromium@429043 702.099 94.4215 18 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 661922 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.intl_ko_th_vi Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___kenh14.vn_home.chn Relative Change: 5.74% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2723 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997022910690041520 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6186052744642560 | 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!
,
Feb 3 2017
These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.
,
Mar 14 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by primiano@chromium.org
, Nov 3 2016