New issue
Advanced search Search tips

Issue 806787 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

TabsTest#testHideKeyboard fails on Android N

Reported by mirko.r...@mips.com, Jan 29 2018

Issue description

Steps to reproduce the problem:
1. Use Android N (I used Nexus 10 with custom rom for Nougat 7.1.1, but it can also be reproduced on qemu with Nougat 7.1.1)
2. ./out/Release/bin/run_chrome_public_test_apk -f org.chromium.chrome.browser.TabsTest#testHideKeyboard

What is the expected behavior?
Test to pass

What went wrong?
Test failed with error:
C   38.872s Main  [FAIL] org.chromium.chrome.browser.TabsTest#testHideKeyboard:
C   38.872s Main  java.lang.AssertionError: expected keyboard show: false
C   38.872s Main  	at org.junit.Assert.fail(Assert.java:88)
C   38.872s Main  	at org.junit.Assert.assertTrue(Assert.java:41)
C   38.872s Main  	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:93)
C   38.872s Main  	at org.chromium.content.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:172)
C   38.872s Main  	at org.chromium.content.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:194)
C   38.872s Main  	at org.chromium.chrome.browser.TabsTest.assertWaitForKeyboardStatus(TabsTest.java:299)
C   38.872s Main  	at org.chromium.chrome.browser.TabsTest.testHideKeyboard(TabsTest.java:335)
C   38.872s Main  	at java.lang.reflect.Method.invoke(Method.java)
C   38.872s Main  	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
C   38.872s Main  	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
C   38.872s Main  	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
C   38.872s Main  	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
C   38.872s Main  	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
C   38.872s Main  	at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:37)
C   38.872s Main  	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
C   38.872s Main  	at org.chromium.chrome.test.ChromeActivityTestRule$1.evaluate(ChromeActivityTestRule.java:113)
C   38.872s Main  	at android.support.test.internal.statement.UiThreadStatement.evaluate(UiThreadStatement.java:55)
C   38.873s Main  	at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:270)
C   38.873s Main  	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
C   38.873s Main  	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
C   38.873s Main  	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
C   38.873s Main  	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:184)
C   38.873s Main  	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:41)
C   38.873s Main  	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
C   38.873s Main  	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
C   38.873s Main  	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
C   38.873s Main  	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
C   38.873s Main  	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
C   38.873s Main  	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
C   38.873s Main  	at org.chromium.base.test.BaseJUnit4ClassRunner.run(BaseJUnit4ClassRunner.java:166)
C   38.873s Main  	at org.junit.runners.Suite.runChild(Suite.java:128)
C   38.873s Main  	at org.junit.runners.Suite.runChild(Suite.java:27)
C   38.873s Main  	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
C   38.873s Main  	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
C   38.873s Main  	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
C   38.873s Main  	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
C   38.873s Main  	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
C   38.873s Main  	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
C   38.873s Main  	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
C   38.873s Main  	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
C   38.873s Main  	at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
C   38.873s Main  	at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262)
C   38.873s Main  	at org.chromium.base.test.BaseChromiumAndroidJUnitRunner.onStart(BaseChromiumAndroidJUnitRunner.java:99)
C   38.873s Main  	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1932)

Did this work before? N/A 

Chrome version: Top of master  Channel: dev
OS Version: Nougat 7.1.1
Flash Version:
 
Cc: changwan@chromium.org ligim...@chromium.org
Components: Tests
Labels: M-66 FoundIn-66 Target-66
Owner: yabinh@chromium.org
Status: Assigned (was: Unconfirmed)
From the stack, assuming test fails at TabsTest.java:335 

Possible suspect, it was committed a while ago.

https://codereview.chromium.org/2290133002

Assigning to the CL owner and looping to one of the reviewers.
Components: UI>Input>Text>IME
Labels: -Pri-2 Pri-3
Owner: ----
Status: Available (was: Assigned)
yabinh@ no longer works on chrome.

I think there are at least two possibilities:
1) UiUtils.isKeyboardShowing() didn't work correctly.
2) fullyLoadUrlInNewTab() didn't work correctly.

Looking at all the disabled tests and retryonfailure annotations in TabsTest.java, I don't think it will be easy to fix this test.

Sign in to add a comment