Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: Verified
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocked on:
issue 662851

Blocking:
issue 667320
issue 667322
issue 667323
issue 667364
issue 667369
issue 673649
issue 674024
issue 683873
issue 683874
issue 683893
issue 684195
issue 684196
issue 684197
issue 684198
issue 684207
issue 684210
issue 684211
issue 684212
issue 684266
issue 684267
issue 684272
issue 684273
issue 684284
issue 684285
issue 684290
issue 684291
issue 684299
issue 684301
issue 684302
issue 684303
issue 684318
issue 684319
issue 684321
issue 684324
issue 684326
issue 684327
issue 684329
issue 684330
issue 684331
issue 684334
issue 684335
issue 684336
issue 684337
issue 684339
issue 684342
issue 684343
issue 684347
issue 684348
issue 684349
issue 684350
issue 684351
issue 684355
issue 684367
issue 684370
issue 684371
issue 684372
issue 684410
issue 684414
issue 684415
issue 684419
issue 684426
issue 684429
issue 684430
issue 684431
issue 684433
issue 684434
issue 684436
issue 684437
issue 684441
issue 684442
issue 684444
issue 684461
issue 684484
issue 684485
issue 684501
issue 684502
issue 684503
issue 684505
issue 684506
issue 684507
issue 684508
issue 684509
issue 684517
issue 684518
issue 684523
issue 684524
issue 684529
issue 684530
issue 684531
issue 684535
issue 684539
issue 684546
issue 684548
issue 684550
issue 684579
issue 684580
issue 684581
issue 684583
issue 684584
issue 684585
issue 684588
issue 684589
issue 684617
issue 684623
issue 684624
issue 684643
issue 684644
issue 684660
issue 684662
issue 684687
issue 684689
issue 684692
issue 684693
issue 684758
issue 684759
issue 684760
issue 684764
issue 684777
issue 684781
issue 684782
issue 684783
issue 684785
issue 684790
issue 684801
issue 684802
issue 684813
issue 684814
issue 684819
issue 684820
issue 684822
issue 684826
issue 684833
issue 684834
issue 684835
issue 684840
issue 684844
issue 684845
issue 684846
issue 684847
issue 684881
issue 684883
issue 684884
issue 684885
issue 684895
issue 684896
issue 684905
issue 684908
issue 684909
issue 684962
issue 684963
issue 684971
issue 684972
issue 684976
issue 684977
issue 684978
issue 684979
issue 684982
issue 684985
issue 684988
issue 684991
issue 684992
issue 684993
issue 684994
issue 684996
issue 684997
issue 684998
issue 685001
issue 685002
issue 685004
issue 685006
issue 685007
issue 685008
issue 685011
issue 685013
issue 685014
issue 685015
issue 685016
issue 685017
issue 685028
issue 685029
issue 685032
issue 685033
issue 685037
issue 685041
issue 685042
issue 685043
issue 685055
issue 685058
issue 685060
issue 685061
issue 685063
issue 685065
issue 685066
issue 685067
issue 685069
issue 685070
issue 685072
issue 685073
issue 685076
issue 685079
issue 685080
issue 685081
issue 685082
issue 685083
issue 685087
issue 685090
issue 685091
issue 685092
issue 685097
issue 685098
issue 685103
issue 685104
issue 685124
issue 685125
issue 685126
issue 685127
issue 685133
issue 685134
issue 685135
issue 685136
issue 685390
issue 685391
issue 685400
issue 685402
issue 685403
issue 685404



Sign in to add a comment
video_ChromeHWDecodeUsed failures in CQ / PFQ
Project Member Reported by steve...@chromium.org, Dec 14 2016 Back to list
There are a huge number of autofiled issues with the following symptom, several per week:

Reason:
Media.GpuVideoDecoderInitializeStatus not loaded or histogram bucket not found or histogram bucket found at < 100%.

Query:
https://bugs.chromium.org/p/chromium/issues/list?can=2&q=video_ChromeHWDecodeUsed

Filing this as a tracking bug for these failures, and linking some of the more recent failures.


 
A note that is also a ping. Still failing. https://luci-milo.appspot.com/buildbot/chromeos/lumpy-chrome-pfq/9549
Comment 2 by ihf@chromium.org, Jan 6 2017
Components: OS>Kernel>Video
Owner: posciak@chromium.org
I took a brief look at the previous link. HW decode on lumpy failed. Nothing in the kernel/chrome logs though.

http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=94587667

The same DUT ran video_VideoSanity.vp8 before and passed, which is of course software decode.

https://uberchromeos-server38.corp.google.com/new_tko/#tab_id=spreadsheet_view&row=job_tag&column=subdir&condition=afe_job_id+%3D+94587667+AND+hostname+%3D+''+AND+test_name+%3D+'video_ChromeHWDecodeUsed'&show_incomplete=true
https://uberchromeos-server38.corp.google.com/new_tko/#tab_id=test_detail_view&object_id=410207066
Comment 3 by ihf@chromium.org, Jan 6 2017
Overall the behavior of the test is not terrible, but on occasion there are problems.
https://wmatrix.googleplex.com/unfiltered?hide_missing=True&tests=video_ChromeHWDecodeUsed&days_back=10
Comment 4 by vsu...@google.com, Jan 7 2017
Cc: vsu...@chromium.org
Labels: OS-Chrome
Cc: rohi...@chromium.org avkodipelli@chromium.org
Could be relevant to  issue 652793  which is duped into   issue 602295 
Cc: warx@chromium.org
Chrome on Chrome OS gardener here (out sick, but looking in anyway). warx@ is  seeing persistent failures on these tests over the last 12 hours or so:

https://bugs.chromium.org/p/chromium/issues/list?can=2&q=video_ChromeHWDecodeUsed&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

For example on tricky:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational

A histograms-related CL landed recently. I'm not sure if that's related or not. Details at  issue 602295 .

Any idea if something changed recently with these tests?

We are working on a bisect now. Range is #445466 - #445545.

I suspect: https://codereview.chromium.org/2640573002 or https://codereview.chromium.org/2628133002

(We should file a separate issue to track this, it's clearly a recent regression)
Comment 8 by ihf@chromium.org, Jan 24 2017
I was setting up my bisect, but I will let you go ahead. Just curious, is it broken video or broken histogram?
The test error result is:

video_ChromeHWDecodeUsed: ERROR: Media.GpuVideoDecoderInitializeStatus not loaded or histogram bucket not found or histogram bucket found at < 100%, new report

FWIW, the chrome log contains a warning, but I haven't checked to see whether the warning is "normal":

WARNING:vaapi_video_decode_accelerator.cc(299)] Picture id 11 does not exist

Comment 10 by ihf@chromium.org, Jan 24 2017
Some logs may suggest broken GPU.

Now I did build ToT Chrome at 445829 + 58.0.2992.0 image on Samus and hardware decode works (Flash h264).

html5 h264 decode seems not to work with the test. White tab. Video right clickable but does not play.

test_that $DUT video_ChromeHWDecodeUsed.h264
Comment 11 by ihf@chromium.org, Jan 24 2017
vp8/vp9 video plays, but does not report it did.

Comment 12 by warx@chromium.org, Jan 24 2017
Constant failure starts on #3260 tricky-tot-chrome-pfq-informational with last revision 445545.

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/chrome_pfq_informational/builds/21

This is what I ran for this revision on peach_pit (excuse me for this not tricky, peach_pit hits the same errors and I just submitted new test for tricky).

It should fail but it pass. Any ideas?
To clarify "should fail" - it is failing consistently on tricky-tot-chrome-pfq-informational, peach_pit-tot-chrome-pfq-informational, and many (but not all) of the PFQ builders.

I have no idea why it did not fail on the tryserver; it appears to be running the bvt-cq stage, but the output is pretty sparse.


Comment 14 by warx@chromium.org, Jan 25 2017
I did some tests on my local peach_pit device, with chromeos version 9217.0 (not tot, but lastest), and then run video_ChromeHWDecodeUsed.h264.mse tests.

Chromium revision #445466 fails the test, even the first revision of latest successful tricky build #445400 fails the test.

that should tell it is not revision from chromium that breaks this?
Labels: videoshortlist
ihf@: for #10 and #11, did you build Chrome with branding/proprietary codecs enabled? If not, that would explain why H264 didn't work, but VP8/9 did.
Comment 17 by warx@chromium.org, Jan 25 2017
fyi, for comment 14, I didn't do "build Chrome with branding/proprietary codecs enabled"
Comment 18 by ihf@chromium.org, Jan 25 2017
Re 16: I had an external checkout as I recently switched my machine. So it was without the cros chrome-sdk --internal flag (and hence without proprietary codecs).
Comment 19 by warx@chromium.org, Jan 25 2017
local DUT bisect shows the culprit CL is: https://codereview.chromium.org/2647353003, reverted CL is created at: https://codereview.chromium.org/2649973007/
For discussion of culprit CL see  issue 602295  Include Persistent Histograms in chrome://histograms
https://codereview.chromium.org/2658163002/ now forces a full merge of histograms from all sub-processes with every load of chrome://histograms so I should be able to again land the enable-by-default of the persistent histograms experiment and not cause a problem with these builds.

Is there any way you can verify this before-hand?

Comment 22 by warx@chromium.org, Feb 1 2017
Cc: x...@chromium.org
It has to run tests locally on chromebook. I see it is already landed. +xdai@ for this week's gardener to track.
Comment 23 by x...@chromium.org, Feb 1 2017
Re#22: Thanks! Seems all the informational builders are quite happy. So I think this CL should be fine.
Status: Fixed
Labels: VerifyIn-59
Sign in to add a comment