camera_V4L2 on elm/sand/reef: [Error] First frame is not a valid mjpeg image. |
||||||
Issue descriptionIt's first failure on elm 9953.0.0 https://wmatrix.googleplex.com/failures/unfiltered?platforms=elm&tests=camera_V4L2&days_back=30&builds=R63-9953.0.0&releases=63&hide_missing=True ~40% flakiness on sand 9953.0.0 https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/142985654-chromeos-test/chromeos2-row3-rack5-host17 9949.0.0 https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/142637901-chromeos-test/chromeos2-row3-rack5-host13 [Info] TestFirstFrameAfterStreamOn <<< Warning: VIDIOC_CROPCAP not supported.>>> <<< Error: VIDIOC_S_CTRL failed. 22>>> actual format for capture 640x480 MJPG picture at 30.00 fps [Error] First frame is not a valid mjpeg image. <<< Error: VIDIOC_REQBUFS for MMAP failed on /dev/video0: Device or resource busy.>>>
,
Sep 20 2017
Vincent, can we get some comments from partners? Thanks.
,
Sep 20 2017
I have opened a bug on buganizer: https://issuetracker.google.com/66181658 for looping in ODM / vendor for further investigation and possible on firmware updates.
,
Sep 29 2017
Seems to be happening on reef too.
,
Sep 29 2017
,
Sep 29 2017
We plan to add a config to skip frames after stream on. For devices which are not launched, we still wish vendor can fix it in camera firmware. For launched devices, we can add the config to disable the alert in test since HAL will skip invalid JPEG. And we can check config to know which devices have this issue.
,
Oct 24 2017
After offline discussion, we disable the test in devices which don't use camera HAL v3 since this is a new requirement. Here is the new patch https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/730365/2
,
Oct 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/ca20001cb896d63e0fb88c1d1a4da0c89e9633b7 commit ca20001cb896d63e0fb88c1d1a4da0c89e9633b7 Author: Heng-Ruey Hsu <henryhsu@chromium.org> Date: Wed Oct 25 10:58:52 2017 camera_V4L2: Add hal v3 test list Constant framerate and valid first frame test are new requirements. We only test them in devices which enable camera hal v3. BUG= chromium:766413 TEST=test_that ${IP} camera_V4L2 pass Change-Id: I64194abd51e828e35121c9fa1737e734ab618ad4 Reviewed-on: https://chromium-review.googlesource.com/730365 Commit-Ready: Heng-ruey Hsu <henryhsu@chromium.org> Tested-by: Heng-ruey Hsu <henryhsu@chromium.org> Reviewed-by: Heng-ruey Hsu <henryhsu@chromium.org> [modify] https://crrev.com/ca20001cb896d63e0fb88c1d1a4da0c89e9633b7/client/site_tests/camera_V4L2/src/media_v4l2_unittest.cc [modify] https://crrev.com/ca20001cb896d63e0fb88c1d1a4da0c89e9633b7/client/site_tests/camera_V4L2/src/media_v4l2_test.cc [modify] https://crrev.com/ca20001cb896d63e0fb88c1d1a4da0c89e9633b7/client/site_tests/camera_V4L2/camera_V4L2.py [delete] https://crrev.com/b8c76b8cc858f1c16e56b96d4cb8405991b9b2cd/client/site_tests/camera_V4L2/control.constant_framerate
,
Oct 26 2017
,
Mar 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/fd838b277c41b1927f20b9b54a7aa206fefd305d commit fd838b277c41b1927f20b9b54a7aa206fefd305d Author: Heng-Ruey Hsu <henryhsu@chromium.org> Date: Mon Mar 26 15:44:17 2018 camera_V4L2: refine maximum resolution test BUG= chromium:766413 TEST=test_that -b ${BOARD} camera_V4L2 Change-Id: If4bbcb98d9310f65e6f660001a5b05c718de9ac5 Reviewed-on: https://chromium-review.googlesource.com/734923 Commit-Ready: Heng-ruey Hsu <henryhsu@chromium.org> Tested-by: Heng-ruey Hsu <henryhsu@chromium.org> Reviewed-by: Ricky Liang <jcliang@chromium.org> [modify] https://crrev.com/fd838b277c41b1927f20b9b54a7aa206fefd305d/client/site_tests/camera_V4L2/src/media_v4l2_test.cc |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by henryhsu@chromium.org
, Sep 20 2017Owner: yueherngl@chromium.org