New issue
Advanced search Search tips

Issue 907132 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Nov 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

peach_pit-chrome-pfq failed at video_ChromeRTCHWDecodeUsed.vp8

Project Member Reported by agawronska@chromium.org, Nov 20

Issue description

video_ChromeRTCHWDecodeUsed.vp8: retry_count: 2, ERROR: Expect Media.RTCVideoDecoderInitDecodeSucces has 1. Histogram: {0: 1}

11/20 05:23:37.181 DEBUG|             utils:0219| Running 'logger "autotest finished iteration /usr/local/autotest/results/default/video_ChromeRTCHWDecodeUsed.vp8/sysinfo/iteration.1"'
11/20 05:23:37.182 DEBUG|      global_hooks:0056| 'logger "autotest finished iteration /usr/local/autotest/results/default/video_ChromeRTCHWDecodeUsed.vp8/sysinfo/iteration.1"'
11/20 05:23:37.202 DEBUG|              test:0391| after_iteration_hooks completed
11/20 05:23:37.203 WARNI|              test:0606| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/common_lib/test.py", line 800, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/common_lib/test.py", line 464, in execute
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/common_lib/test.py", line 371, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/cros/video/helper_logger.py", line 82, in call
    return func(*args, **kwargs)
  File "/usr/local/autotest/tests/video_ChromeRTCHWDecodeUsed/video_ChromeRTCHWDecodeUsed.py", line 91, in run_once
    histogram_differ, histogram_bucket_val, histogram_bucket_val)
  File "/usr/local/autotest/cros/video/histogram_verifier.py", line 197, in expect_sole_bucket
    (histogram_name, bucket_name, histogram))
TestError: Expect Media.RTCVideoDecoderInitDecodeSucces has 1. Histogram: {0: 1}
 
Owner: posciak@chromium.org
Pawel, Can you have a look at that or help to find the right owner?
It also fails on peach_pit-tot-chrome-pfq-informational.

Cc: -hiroh@chromium.org akahuang@chromium.org
Owner: hiroh@chromium.org
Status: Assigned (was: Available)
hiroh@: could this be related to any recent changes in V4L2VEA? Chrome error logs contain:

[4046:4697:1120/052325.467319:VERBOSE2:v4l2_video_decode_accelerator.cc(2174)] CreateInputBuffers(): 
[4046:4081:1120/052325.481543:VERBOSE2:v4l2_video_encode_accelerator.cc(158)] Initialize(): : input_format: PIXEL_FORMAT_I420, input_visible_size: 1280x720, output_profile: vp8, initial_bitrate: 300000, initial_framerate: 30
[4046:4697:1120/052325.512950:VERBOSE2:v4l2_video_decode_accelerator.cc(1697)] IsDecoderCmdSupported(): V4L2_DEC_CMD_STOP is not supported.
[4046:4081:1120/052325.514284:VERBOSE2:v4l2_video_encode_accelerator.cc(188)] Initialize(): V4L2_ENC_CMD_STOP is not supported.
[4046:4081:1120/052325.514389:VERBOSE2:v4l2_video_encode_accelerator.cc(1175)] SetFormats(): 
[4046:4081:1120/052325.514644:VERBOSE2:v4l2_video_encode_accelerator.cc(1107)] NegotiateInputFormat(): 
[4046:4081:1120/052325.514772:VERBOSE2:v4l2_video_encode_accelerator.cc(1204)] SetFormats(): Fallback to VIDIOC_S/G_CROP
[4046:4081:1120/052325.514868:VERBOSE2:v4l2_video_encode_accelerator.cc(1215)] SetFormats(): After adjusted by driver, visible_size_=1280x720
[4046:4081:1120/052325.514958:VERBOSE2:v4l2_video_encode_accelerator.cc(205)] Initialize(): Input format not supported by the HW, will try to convert to PIXEL_FORMAT_NV12
[4046:4081:1120/052325.516140:FATAL:v4l2_device.cc(888)] Add more cases as needed


So we are hitting a nonimplemented case in V4L2Device::VideoPixelFormatToV4L2PixFmt().
 Issue 907381  has been merged into this issue.
Project Member

Comment 7 by bugdroid1@chromium.org, Nov 21

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f1abe1e001199d15e7b15e15ab3864809cf31aa7

commit f1abe1e001199d15e7b15e15ab3864809cf31aa7
Author: Hirokazu Honda <hiroh@chromium.org>
Date: Wed Nov 21 07:26:07 2018

media/gpu/V4L2VEA: Fix wrong V4L2PixFmtToVideoPixelFormat call on V4L2VEA

V4L2VEA wrongly calls V4L2Device::V4L2PixFmtToVideoPixelFormat to
VideoPixelFormat in VideoFrameLayout::Create. Just pass the VideoPixelFormat
without calling.

BUG= chromium:907132 
TEST=VEA unittest on peach_pit

Change-Id: I3800cc81403a19e7521f724f972f63e937f0873b
Reviewed-on: https://chromium-review.googlesource.com/c/1345700
Reviewed-by: Pawel Osciak <posciak@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#609936}
[modify] https://crrev.com/f1abe1e001199d15e7b15e15ab3864809cf31aa7/media/gpu/v4l2/v4l2_video_encode_accelerator.cc

Thank you. Informational-pfq is down right now, because of the ifra migration. I will verify that it is fixed after migration.
The build [1] is pass now which includes comment#7 patch (landed on chrome 72.0.3618.0)

[1]: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8929173554818900832

Status: Verified (was: Assigned)

Sign in to add a comment