New issue
Advanced search Search tips

Issue 747867 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

54.1% regression in media.tough_video_cases_tbmv2 at 487916:488051

Project Member Reported by hjd@google.com, Jul 24 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 24 2017

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=747867

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=bfa8cac3c63c56aad3b38faeb3e2335ea660258f0dbcd0e0dca2366dbc90933a


Bot(s) for this bug's original alert(s):

win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 24 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_avg/video.html?src_tulip2.mp3_type_audio

Revision             Result                  N
chromium@487915      7.40996 +- 3.38731      21      good
chromium@488051      7.30924 +- 2.71857      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.tulip2.mp3.type.audio media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973193420060750080


For feedback, file a bug with component Speed>Bisection

Comment 5 by hjd@chromium.org, Jul 24 2017

Kicked off a much wider bisect (487350-488674)
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 24 2017

Labels: Hotlist-Google
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Jul 24 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_avg/video.html?src_tulip2.mp3_type_audio

Revision             Result                  N
chromium@487350      8.24168 +- 2.19988      21      good
chromium@488674      8.31825 +- 2.13065      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.tulip2.mp3.type.audio media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973184782292674112


For feedback, file a bug with component Speed>Bisection

Comment 8 by hjd@chromium.org, Jul 25 2017

Status: WontFix (was: Untriaged)
Bisect failed twice and a random sampling of the benchmarks showed no movement.
The ref is missing.

Sign in to add a comment