Issue metadata
Sign in to add a comment
|
6.5%-52.6% regression in media.android.tough_video_cases at 408133:408192 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005558433800455504
,
Aug 1 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@408136 120.157 8.64689 12 good chromium@408179 117.215 9.38421 12 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 633035 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases Test Metric: buffering_time/crowd.wav Relative Change: 1.14% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/404 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005558433800455504 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5835340217057280 | 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!
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005516797545909184
,
Aug 1 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005509244835870688
,
Aug 1 2016
Bisect failed: Unknown Failure reason: the build has failed due to infrastructure failure.
,
Aug 2 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9005418031874610752
,
Aug 2 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@408136 324.159 33.4892 14 good chromium@408192 313.126 20.305 12 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 633035 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases Test Metric: time_to_play/tulip2.webm Relative Change: 6.05% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3906 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005509244835870688 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5870033889132544 | 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!
,
Aug 18 2016
Perf sheriff ping: reminder to follow up on possible performance issues
,
Sep 22 2016
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by hubbe@chromium.org
, Aug 1 2016