Issue metadata
Sign in to add a comment
|
6.4%-75.3% regression in page_cycler_v2.top_10_mobile at 419843:424532 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 12 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8998979895202498320
,
Oct 12 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@424445 161.034 6.18264 18 good chromium@424448 157.85 4.19357 18 bad Bisect job ran on: linux_perf_bisect Bug ID: 655254 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.top_10_mobile Test Metric: timeToFirstMeaningfulPaint_avg/pcv1-cold/http___m.youtube.com_results?q_science Relative Change: 2.62% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6778 Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998979895202498320 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5298885998673920 | 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 26 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8997726612358124336
,
Oct 26 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/764 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.
,
Jan 6 2017
Archiving as bisection is difficult and there's been no movement. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Oct 12 2016