Issue metadata
Sign in to add a comment
|
22.1%-55.3% regression in media.android.tough_video_cases at 436613:449556 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987733911751014448
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982580438161918512
,
Apr 11 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : media.android.tough_video_cases Metric : vm_proportional_set_size_delta/smpte_3840x2160_60fps_vp9.webm_renderer To Run This Test src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests media.android.tough_video_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982580438161918512 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5799683504472064 | 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 Speed>Bisection. Thank you!
,
Oct 30 2017
,
Nov 14 2017
WontFix. Bisect didn't work and bug is stale. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jrumm...@chromium.org
, Feb 13 2017