Issue metadata
Sign in to add a comment
|
39.3%-521.9% regression in page_cycler_v2.tough_layout_cases at 419322:419370 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 20 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000989670525664432
,
Sep 20 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/805 Failure reason: the build has failed. Additional errors: The metric was not found in the test output. Either of the initial "good" or "bad" revisions failed to be tested or built.
,
Sep 20 2016
,
Sep 22 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000778493743324144
,
Sep 23 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@419321 211.398 57.325 18 good chromium@419368 191.175 25.9753 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 648616 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.tough_layout_cases Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___indoritel.com Relative Change: 2.81% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1677 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000778493743324144 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5900381119315968 | 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 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9000430192460687872
,
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@419321 197.255 48.297 18 good chromium@419368 190.387 20.7681 18 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 648616 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.tough_layout_cases Test Metric: timeToFirstContentfulPaint_avg/pcv1-warm/http___indoritel.com Relative Change: 5.80% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1691 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000430192460687872 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5828892395307008 | 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!
,
Oct 6 2016
perf sheriff fixit: unassigning bugs owned by perf sheriffs to clarify that the rotation is responsible for triage.
,
Nov 22 2016
,
Jan 6 2017
Archiving as bisection is difficult and there's been no movement.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651535923196336
,
Apr 11 2017
Bisect failed: None Failure reason: incorrect bisect configuation. Additional errors: The metric was not found in the test output. Either of the initial "good" or "bad" revisions failed to be tested or built. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by jasontiller@chromium.org
, Sep 20 2016