Issue metadata
Sign in to add a comment
|
37.1%-63.3% regression in page_cycler_v2.tough_layout_cases at 415578:415614 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001971329120202192
,
Sep 9 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6918 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 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001963874918417520
,
Sep 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001963871102511184
,
Sep 9 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2553 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 9 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6921 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 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001683584280219072
,
Sep 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001683570816091056
,
Sep 13 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2555 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 13 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6924 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 13 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001669013499977984
,
Sep 13 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001669005839407408
,
Sep 13 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2557 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 13 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6930 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
,
Oct 3 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8999798656957848320
,
Oct 3 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@415590 72.1859 10.2831 18 good chromium@415614 67.1422 6.08692 18 bad Bisect job ran on: android_nexus6_perf_bisect Bug ID: 645567 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.basic_oopif Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___www.fifa.com_ Relative Change: 11.04% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2597 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999798656957848320 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5887292374253568 | 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: removing owners from bugs owned by the sheriffs who filed them to clarify that the rotation triages the bugs.
,
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/8982651923627127440
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982620313721891168
,
Apr 11 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : page_cycler_v2.basic_oopif Metric : pcv1-cold-timeToFirstMeaningfulPaint_avg/http___www.fifa.com_ To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler_v2.basic_oopif Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982651923627127440 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5162090073948160 | 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 Speed>Bisection. Thank you!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982576189073631280 |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by rsch...@chromium.org
, Sep 9 2016