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

Issue 660952 link

Starred by 1 user
Status: WontFix
Owner:
█ avayvod@chromium.org
Last visit > 30 days ago
Closed: Nov 2016
Cc:
█ zqzh...@chromium.org
mfo...@chromium.org
█ x...@chromium.org
btolsch@chromium.org
powerb@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

org.chromium.chrome.browser.media.router.MediaRouterIntegrationTest_testBasic flaky due to missing device permission.

Project Member Reported by dalecur...@chromium.org, Oct 31 2016 
org.chromium.chrome.browser.media.router.MediaRouterIntegrationTest#testBasic (run #1):
java.lang.SecurityException: Injecting to another application requires INJECT_EVENTS permission
	at android.os.Parcel.readException(Parcel.java:1465)
	at android.os.Parcel.readException(Parcel.java:1419)
	at android.hardware.input.IInputManager$Stub$Proxy.injectInputEvent(IInputManager.java:356)
	at android.hardware.input.InputManager.injectInputEvent(InputManager.java:641)
	at android.app.Instrumentation.sendPointerSync(Instrumentation.java:937)
	at org.chromium.chrome.browser.media.RouterTestUtils.sendMouseAction(RouterTestUtils.java:153)
	at org.chromium.chrome.browser.media.RouterTestUtils.mouseSingleClick(RouterTestUtils.java:166)
	at org.chromium.chrome.browser.media.RouterTestUtils.mouseSingleClickView(RouterTestUtils.java:183)
	at org.chromium.chrome.browser.media.RouterTestUtils.mouseSingleClickView(RouterTestUtils.java:195)
	at org.chromium.chrome.browser.media.router.MediaRouterIntegrationTest.testBasic(MediaRouterIntegrationTest.java:216)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:192)
	at org.chromium.chrome.test.ChromeActivityTestCaseBase.runTest(ChromeActivityTestCaseBase.java:726)
	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

from https://uberchromegw.corp.google.com/i/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/36820

Seems like this is due to a missing permission.

Comment 1 by dalecur...@chromium.org, Oct 31 2016

Labels: -OS-Linux

Comment 2 by mfo...@chromium.org, Oct 31 2016

Cc: zqzh...@chromium.org
Components: Blink>PresentationAPI Tests>Flaky
Owner: avayvod@chromium.org
Anton, Zhiqiang, does this ring a bell?

Comment 3 by rsgav...@chromium.org, Nov 2 2016

Status: Assigned (was: Unconfirmed)

Comment 4 by avayvod@chromium.org, Nov 11 2016

Status: WontFix (was: Assigned)
INJECT_EVENTS usually means some other app UI is shown above Chrome (e.g. the "This app crashed" dialog if some test crashed before) so the current test is trying to send keyboard or mouse events to another app instead of itself. It's a common failure reason for Android instrumentation tests it's only fixed by preventing the previous crashes, not something the test failing with INJECT_EVENTS can do.
I didn't find anything suggesting what was on top of Chrome in the test runner logs so I don't think there's anything to follow up with.
►

Sign in to add a comment