Issue metadata
Sign in to add a comment
|
3.3%-997.4% regression in smoothness.top_25_smooth at 414514:414559 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 9 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001974056445565152
,
Sep 9 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@414536 61.7317 22.6637 18 good chromium@414552 76.7493 56.5955 18 bad Bisect job ran on: mac_10_11_perf_bisect Bug ID: 645535 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth Test Metric: first_gesture_scroll_update_latency/http___sports.yahoo.com_ Relative Change: 19.40% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/882 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001974056445565152 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5788084308803584 | 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 13 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001681092907602096
,
Sep 13 2016
Lotta noisy alerts here. Tried to bisect on the clear ones.
,
Sep 13 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/891 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/9001669068183032352
,
Sep 13 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9001669027623252768
,
Sep 13 2016
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/892 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/mac_10_11_perf_bisect/builds/893 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.
,
Oct 6 2016
There are a lot of possible CLs, but without bisect, it's hard to tell. Possible CLs: https://chromium.googlesource.com/chromium/src/+log/336d51f5105c5079da6bd099b6e3843fc759a46b%5E..540ba6cbe242920544a1f43019e4f4a3c6f81bf8?pretty=fuller Also, the performance un-regressed after this range of CLs (lots of reverts): https://chromium.googlesource.com/chromium/src/+log/df9cb098cf816fb589e0ad6627012b524c78e9eb%5E..6b6ec1c01c7dac3ee76f9245e4ee442f1c669c55?pretty=fuller It's unclear what broke this, but it was resolved after a bit. Won'tFix.
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982584492710075072 |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by rsch...@chromium.org
, Sep 9 2016