New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 607326 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

video_ChromeHWDecodeUsed test flaking out on many different machines

Reported by dhend...@chromium.org, Apr 27 2016

Issue description

We've been seeing this issue recently:
video_ChromeHWDecodeUsed                ERROR: Media.GpuVideoDecoderInitializeStatus not loaded or histogram bucket not found or histogram bucket found at < 100%

The issue tracker shows dozens of auto-filed issues, mostly from March 22-23: https://bugs.chromium.org/p/chromium/issues/list?can=1&q=%22not+loaded+or+histogram+bucket+not+found+or+histogram+bucket+found+at%22&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids
 

Comment 1 by h...@chromium.org, Apr 27 2016

Cc: posciak@chromium.org

Comment 2 by h...@chromium.org, Apr 27 2016

Cc: ihf@chromium.org marc...@chromium.org h...@chromium.org
This particular test (video_ChromeHWDecodeUsed) has a long history of flakes

Comment 3 by lpique@chromium.org, Apr 27 2016

The log from the most recent failure: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/61456620-chromeos-test/chromeos2-row3-rack10-host1/video_ChromeHWDecodeUsed/debug/

The test framework navigated to a video page (http://crosvideo.appspot.com/?codec=h264&cycle=true&mute=true), then navigates to chrome://histograms/Media.GpuVideoDecoderInitializeStatus, and reads the text of the page.

The string that was returned only contained some of the expected response

04/27 13:12:12.786 DEBUG|inspector_websocke:0164| got [{
  "id": 31, 
  "result": {
    "result": {
      "type": "string", 
      "value": "Stats accumulated from browser startup to previous page load; reload to get stats as of this page load.\n\n"
    }, 
    "wasThrown": false
  }
}]

If I open the same histogram URL on my browser, I get text that includes a histogram:

    Stats accumulated from browser startup to previous page load; reload to get stats as of this page load.

    Histogram: Media.GpuVideoDecoderInitializeStatus recorded 1 samples, average = 15.0 (flags = 0x1)
    0   ... 
    15  ------------------------------------------------------------------------O (1 = 100.0%) {0.0%}
    16  ... 

Comment 4 by ihf@chromium.org, Apr 28 2016

Labels: M-52 OS-Chrome
Yes, so this is the most basic hardware decode integration test with Chrome: play a video, check that Chrome thinks it used hardware decode. It thinks it didn't. I looked at a few logs, I don't see relevant failures (especially kernel). One would have to debug this locally. But it shows a real problem.
Components: -Internals>GPU>Video OS>Kernel>Video
Labels: VideoShortList

Comment 6 by ihf@chromium.org, Apr 28 2016

High level, I think the most recent failures are starting with build 8236 from Sun April 24th.
https://wmatrix.googleplex.com/unfiltered?hide_missing=True&tests=video_ChromeHWDecodeUsed&days_back=100&releases=52

There may be 2 different failures: Intel and cheets.

Intel could be an OS commit here
https://crosland.corp.google.com/log/8230.0.0..8236.0.0

They cyan-sheets and veyron_minnie-cheets failures are coming from attempts to rev Chrome 52.0.2716.0 into ChromeOS and were probably fixed in Chrome. A bit strange.
Issue 596779 has been merged into this issue.
Issue 596792 has been merged into this issue.
Issue 596801 has been merged into this issue.
Issue 596805 has been merged into this issue.
Issue 596809 has been merged into this issue.
Issue 596884 has been merged into this issue.
Issue 596886 has been merged into this issue.
Issue 596903 has been merged into this issue.
Issue 596912 has been merged into this issue.
Issue 596938 has been merged into this issue.
Issue 596941 has been merged into this issue.
Issue 596966 has been merged into this issue.
Issue 596987 has been merged into this issue.
Issue 597063 has been merged into this issue.
Issue 597074 has been merged into this issue.
Issue 597092 has been merged into this issue.
Issue 597093 has been merged into this issue.
Issue 597108 has been merged into this issue.
Issue 597114 has been merged into this issue.
Issue 597116 has been merged into this issue.
Issue 597129 has been merged into this issue.
Issue 597133 has been merged into this issue.
Issue 597134 has been merged into this issue.
Issue 597182 has been merged into this issue.
Issue 597189 has been merged into this issue.
Issue 597200 has been merged into this issue.
Issue 597201 has been merged into this issue.
Issue 597202 has been merged into this issue.
Issue 597211 has been merged into this issue.
Issue 597271 has been merged into this issue.
Issue 597282 has been merged into this issue.
Issue 597291 has been merged into this issue.
Issue 597305 has been merged into this issue.
Issue 597418 has been merged into this issue.
Issue 597462 has been merged into this issue.
Issue 597468 has been merged into this issue.
Issue 597470 has been merged into this issue.
Issue 597483 has been merged into this issue.
Issue 602071 has been merged into this issue.
Issue 604163 has been merged into this issue.
Issue 604192 has been merged into this issue.
Issue 606194 has been merged into this issue.
Issue 607286 has been merged into this issue.
Status: WontFix (was: Available)
veyron_minnie-cheets failures were due to the main Chrome window was missing the focus which has been fixed. Please re-open if there are any other failures.

Comment 9 by ihf@chromium.org, May 2 2016

Yes, green again since about R52-8252.0.0.

Sign in to add a comment