Issue metadata
Sign in to add a comment
|
1656.9% regression in smoothness.top_25_smooth at 401935:401960 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 28 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@401983 27.1265 6.16784 8 good chromium@402064 22.4513 6.33944 7 bad Bisect job ran on: mac_retina_perf_bisect Bug ID: 623820 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/ESPN Relative Change: 37.56% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1365 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9008649558314827600 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5866954523410432 | 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!
,
Jun 28 2016
,
Jul 2 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 21 2016
The regression was recovered, so make it as wontfix. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by lanwei@google.com
, Jun 28 2016