Issue metadata
Sign in to add a comment
|
1.5%-3.7% regression in media.android.tough_video_cases at 465785:465870 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981691029835852512
,
Apr 21 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : media.android.tough_video_cases Metric : vm_proportional_set_size_delta/tulip2.mp4_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/8981691029835852512 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6674828343377920 | 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!
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981689378423982576
,
Apr 22 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: 4a08ce5f3acdb7170a36da773a696cdcd3e96788 bad_revision : 46d05bbdf9e2faec3d4ff1d245e380d6eecce774 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : media.android.tough_video_cases Metric : vm_proportional_set_size_delta/tulip2.mp4_renderer Revision Result N chromium@465784 8542.42 +- 1055.6 6 good chromium@465827 8553.42 +- 790.597 6 good chromium@465849 8549.06 +- 1140.92 9 good chromium@465855 8635.25 +- 1198.35 14 good chromium@465857 8512.22 +- 830.641 9 good chromium@465858 --- --- build failure chromium@465860 8891.5 +- 1074.55 14 bad chromium@465870 9032.08 +- 254.139 6 bad 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/8981689378423982576 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6674828343377920 | 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!
,
Apr 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981525836367194992
,
Apr 24 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: e4c132b04e4a9b43b9d8db37f0ef7895c53d4fb5 bad_revision : f5f56eaf9aa0338be5de51380df8cf90814e2444 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : media.android.tough_video_cases Metric : vm_proportional_set_size_delta/crowd720_vp9.webm_renderer Revision Result N chromium@465784 24014.5 +- 837.753 6 good chromium@465827 23872.7 +- 1143.79 6 good chromium@465849 24105.0 +- 913.766 14 good chromium@465854 25256.4 +- 3591.76 21 bad chromium@465860 24427.1 +- 1100.73 14 bad chromium@465870 24444.2 +- 654.24 9 bad 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/8981525836367194992 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6674828343377920 | 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!
,
Apr 27 2017
The regression has gone away.
,
May 1 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980812312621088368
,
May 2 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: f5f56eaf9aa0338be5de51380df8cf90814e2444 bad_revision : 7e3b591c123be4a9fc4f789575a1c0ffd7d6af9c If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : media.android.tough_video_cases Metric : vm_proportional_set_size_delta/tulip2.mp4_renderer Revision Result N chromium@465784 8577.92 +- 1153.57 6 good chromium@465827 8499.92 +- 791.588 6 good chromium@465849 8697.61 +- 942.518 14 good chromium@465854 8629.72 +- 864.024 9 good chromium@465859 8951.9 +- 991.761 21 bad chromium@465870 8925.43 +- 863.065 14 bad 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/8980812312621088368 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6674828343377920 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by zhanliang@google.com
, Apr 21 2017