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

Issue 673140 link

Starred by 1 user
Status: Duplicate
Merged: issue 628964
Owner: ----
Closed: Dec 2016
Cc:
█ yabinh@chromium.org
█ aelias@chromium.org
changwan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"org.chromium.content.browser.input.ImeTest#testKeyboardDismissedAfterClickingGo" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Dec 11 2016 
"org.chromium.content.browser.input.ImeTest#testKeyboardDismissedAfterClickingGo" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyWgsSBUZsYWtlIk9vcmcuY2hyb21pdW0uY29udGVudC5icm93c2VyLmlucHV0LkltZVRlc3QjdGVzdEtleWJvYXJkRGlzbWlzc2VkQWZ0ZXJDbGlja2luZ0dvDA.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs

This flaky test/step was previously tracked in  issue 549309 .

Comment 1 by jbudorick@chromium.org, Dec 12 2016

Cc: aelias@chromium.org changwan@chromium.org
The recent linux_android_rel_ng failures are all:

junit.framework.AssertionFailedError: expected:<5> but was:<0>
	at org.chromium.content.browser.input.ImeTest.waitAndVerifyUpdateSelection(ImeTest.java:1544)
	at org.chromium.content.browser.input.ImeTest.testKeyboardDismissedAfterClickingGo(ImeTest.java:134)
	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.content_shell_apk.ContentShellTestBase.runTest(ContentShellTestBase.java:256)
	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)

+cc aelias & changwan as closest owners

Comment 2 by changwan@chromium.org, Dec 13 2016

Cc: yabinh@chromium.org
yabinh@, are we aware of this flakiness?

Comment 3 by yabinh@chromium.org, Dec 13 2016

Mergedinto: 628964
Status: Duplicate (was: Untriaged)
Same as the one in comment#23.
►

Sign in to add a comment