Issue metadata
Sign in to add a comment
|
24.3% regression in media.tough_video_cases_extra at 401812:401832 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 8 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@401811 929.039 10.8459 18 good chromium@401832 927.684 8.03435 18 bad Bisect job ran on: winx64_zen_perf_bisect Bug ID: 626518 Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests media.tough_video_cases_extra Test Metric: seek/crowd1080_vp9.webm_seek_cold Relative Change: 0.55% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/257 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007747274439361936 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5777964109660160 | 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!
,
Jul 8 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 11 2016
Alert was invalid. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by w...@chromium.org
, Jul 8 2016