Issue metadata
Sign in to add a comment
|
78% regression in media.tough_video_cases_tbmv2 at 464497:464668 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981837726723411776
,
Apr 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : idle:power_min/video.html?src_smpte_3840x2160_60fps_vp9.webm Revision Result N chromium@464496 4.48949 +- 4.87039 21 good chromium@464668 4.90515 +- 3.74177 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981837726723411776 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6340184087461888 | 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 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981831462674325840
,
Apr 20 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : idle:power_min/video.html?src_smpte_3840x2160_60fps_vp9.webm Change : 4.39% | 4.11085454929 -> 4.29147602786 Suspected Commit Range 8 commits in range https://chromium.googlesource.com/chromium/src/+log/6f797ffc358c069eb954a59ea811c12d80208feb..fe9df09aa9ddcb6969f2a9eea7223ae5d5d8e9d1 Revision Result N chromium@464496 4.11085 +- 0.659538 14 good chromium@464505 4.12344 +- 0.573749 20 good chromium@464510 4.27199 +- 1.76799 14 good chromium@464511 --- --- build failure chromium@464512 --- --- build failure chromium@464513 --- --- build failure chromium@464514 --- --- build failure chromium@464515 --- --- build failure chromium@464516 --- --- build failure chromium@464517 --- --- build failure chromium@464518 4.44609 +- 1.93764 14 bad chromium@464541 4.45358 +- 1.83391 14 bad chromium@464583 4.27193 +- 0.363511 14 bad chromium@464668 4.29148 +- 0.431575 14 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981831462674325840 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6340184087461888 | 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 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981760811583898208
,
Apr 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : idle:power_min/video.html?src_smpte_3840x2160_60fps_vp9.webm Revision Result N chromium@464496 6.32446 +- 4.00358 21 good chromium@464668 6.63131 +- 3.14181 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981760811583898208 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5864136086388736 | 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 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981755017797638144
,
Apr 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : idle:power_min/video.html?src_smpte_3840x2160_60fps_vp9.webm Revision Result N chromium@464496 6.32446 +- 4.00358 21 good chromium@464668 6.63131 +- 3.14181 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981755017797638144 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5864136086388736 | 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 20 2017
Bisect couldn't find the regression, and the graph on perf dashboard had been noisy lately, and had almost returned to the pre-regression level. There seems to be nothing actionable right now.
,
Apr 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981661992429918816
,
Apr 22 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : idle:power_min/video.html?src_smpte_3840x2160_60fps_vp9.webm Revision Result N chromium@464496 6.48813 +- 4.19424 21 good chromium@464668 6.71442 +- 2.56265 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981661992429918816 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5864136086388736 | 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 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981021501794747424
,
Apr 29 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64_high_dpi_perf_bisect Benchmark : media.tough_video_cases_tbmv2 Metric : idle:power_min/video.html?src_smpte_3840x2160_60fps_vp9.webm Revision Result N chromium@464496 4.48921 +- 2.48743 21 good chromium@464668 4.28047 +- 1.31928 21 bad To Run This Test src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.smpte.3840x2160.60fps.vp9.webm media.tough_video_cases_tbmv2 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981021501794747424 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5864136086388736 | 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 20 2017