New issue
Advanced search Search tips

Issue 709039 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Flaky-Test: VideoCaptureBrowserTest.ReceiveFramesFromFakeCaptureDevice



Sign in to add a comment

VideoCaptureBrowserTest.ReceiveFramesFromFakeCaptureDevice/4 flaky on android

Project Member Reported by ellyjo...@chromium.org, Apr 6 2017

Issue description

https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.linux%2FAndroid_Tests__dbg_%2F41506%2F%2B%2Frecipes%2Fsteps%2Fcontent_browsertests_on_Android%2F0%2Flogs%2FVideoCaptureBrowserTest.ReceiveFramesFromFakeCaptureDevice_4%2F0

VideoCaptureBrowserTest.ReceiveFramesFromFakeCaptureDevice/4 (run #1):
[ RUN      ] VideoCaptureBrowserTest.ReceiveFramesFromFakeCaptureDevice/4
[WARNING:dns_config_service_posix.cc(326)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(221)] Cannot start http server for devtools. Stop devtools.

GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: Opened(2, 1)
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to enforce the call.  See http://code.google.com/p/googlemock/wiki/CookBook#Knowing_When_to_Expect for details.

GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: OnStarted(123)
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to enforce the call.  See http://code.google.com/p/googlemock/wiki/CookBook#Knowing_When_to_Expect for details.
[INFO:SkFontMgr_android_parser.cpp(609)] [SkFontMgr Android Parser] '/system/etc/fonts.xml' could not be opened

[INFO:SkFontMgr_android_parser.cpp(609)] [SkFontMgr Android Parser] '/vendor/etc/fallback_fonts.xml' could not be opened

BrowserTestBase received signal: Segmentation fault. Backtrace:

chfremer@, can you take a look or route this to someone else please?
 
Sorry about the test flakiness. 

Let me go ahead and disable the test on Android until I can figure out what is causing this. It should be okay to disable, because the tested code path is currently not active in production on Android.
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 6 2017

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

commit 600a408935228895ee63feb521044723f5fa23a2
Author: chfremer <chfremer@chromium.org>
Date: Thu Apr 06 19:06:55 2017

Disable test case ReceiveFramesFromFakeCaptureDevice/4 on Android

This test case was recently added [1] to exercise a code path for accelerated
MJPEG decoding that is currently only in production use on Chromium OS and was
previously not covered by any Chromium tests.

This test case appears to fail intermittently on Android.
This CL disables the test case for Android in order to mitigate the test
flakiness it causes.

[1] https://codereview.chromium.org/2772963002/

BUG=709039
TEST=content_browsertests --gtest_filter="VideoCaptureBrowserTest.*"

Review-Url: https://codereview.chromium.org/2803593006
Cr-Commit-Position: refs/heads/master@{#462570}

[modify] https://crrev.com/600a408935228895ee63feb521044723f5fa23a2/content/browser/renderer_host/media/video_capture_browsertest.cc

Project Member

Comment 6 by bugdroid, Today (9 minutes ago)

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

commit fecb029e6187fbceb05679b0489968532de9ee28
Author: Christian Fremerey <chfremer@chromium.org>
Date: Thu Jan 24 01:11:08 2019

[Video Capture, Android] Re-enable tests involving accelerated jpeg decoding

Re-enable video capture tests involving accelerated jpeg decoding on
Android that used to be flaky.

There have been a lot of fixes in the video capture pipeline since these
test cases were disabled. The tests pass when running locally. It is worth
re-enabling. If they turn out to still produce flakiness, we can disable
again and use the produced logs to investigate.

Bug: 709039
Change-Id: Ib6c8631a2cc178b1c767fb674cae4e52990f4e87
Reviewed-on: https://chromium-review.googlesource.com/c/1422462
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Reviewed-by: Weiyong Yao <braveyao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#625465}

Sign in to add a comment