Two tests failing on phones (e.g. Nexus 5X)
Reported by
kra...@amazon.com,
Mar 27 2017
|
|||
Issue descriptionChrome Version: Close to tip of master (SHA: c85bdf433f16428084e93da3b24bf5e86e0f117e) OS: Android What steps will reproduce the problem? (1) Run OmniboxTest#testSuggestionDirectionSwitching or SuggestionsBottomSheetTest#testContextMenu on a Nexus 5X or several other phones What is the expected result? The test passes What happens instead? I 28.476s Main FINISHED TRY #1/1 I 28.476s Main 1 failed tests remain. C 28.476s Main ******************************************************************************** C 28.476s Main Detailed Logs C 28.476s Main ******************************************************************************** C 28.477s Main [FAIL] org.chromium.chrome.browser.omnibox.OmniboxTest#testSuggestionDirectionSwitching: C 28.477s Main junit.framework.AssertionFailedError: Tab never selected/initialized. C 28.477s Main at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:79) C 28.477s Main at org.chromium.content.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:117) C 28.477s Main at org.chromium.content.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:138) C 28.477s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.startMainActivityFromIntent(ChromeActivityTestCaseBase.java:465) C 28.477s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.startMainActivityWithURL(ChromeActivityTestCaseBase.java:429) C 28.477s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.startMainActivityOnBlankPage(ChromeActivityTestCaseBase.java:437) C 28.477s Main at org.chromium.chrome.browser.omnibox.OmniboxTest.startMainActivity(OmniboxTest.java:761) C 28.477s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.setUp(ChromeActivityTestCaseBase.java:144) C 28.477s Main at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161) C 28.477s Main at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124) C 28.477s Main at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:198) C 28.477s Main at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:183) C 28.477s Main at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:560) C 28.477s Main at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1932) C 28.477s Main ******************************************************************************** C 28.477s Main Summary C 28.477s Main ******************************************************************************** C 28.477s Main [==========] 1 test ran. C 28.477s Main [ PASSED ] 0 tests. C 28.477s Main [ FAILED ] 1 test, listed below: C 28.477s Main [ FAILED ] org.chromium.chrome.browser.omnibox.OmniboxTest#testSuggestionDirectionSwitching C 28.478s Main C 28.478s Main 1 FAILED TEST C 28.478s Main ******************************************************************************** I 111.345s Main FINISHED TRY #1/1 I 111.345s Main 1 failed tests remain. C 111.346s Main ******************************************************************************** C 111.346s Main Detailed Logs C 111.346s Main ******************************************************************************** C 111.346s Main [FAIL] org.chromium.chrome.browser.suggestions.SuggestionsBottomSheetTest#testContextMenu: C 111.346s Main junit.framework.AssertionFailedError: Tab never selected/initialized. C 111.346s Main at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:79) C 111.346s Main at org.chromium.content.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:117) C 111.346s Main at org.chromium.content.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:138) C 111.346s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.startMainActivityFromIntent(ChromeActivityTestCaseBase.java:465) C 111.346s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.startMainActivityWithURL(ChromeActivityTestCaseBase.java:429) C 111.346s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.startMainActivityOnBlankPage(ChromeActivityTestCaseBase.java:437) C 111.346s Main at org.chromium.chrome.test.BottomSheetTestCaseBase.startMainActivity(BottomSheetTestCaseBase.java:57) C 111.346s Main at org.chromium.chrome.test.ChromeActivityTestCaseBase.setUp(ChromeActivityTestCaseBase.java:144) C 111.346s Main at org.chromium.chrome.test.BottomSheetTestCaseBase.setUp(BottomSheetTestCaseBase.java:38) C 111.346s Main at org.chromium.chrome.browser.suggestions.SuggestionsBottomSheetTest.setUp(SuggestionsBottomSheetTest.java:36) C 111.346s Main at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161) C 111.346s Main at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124) C 111.346s Main at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:198) C 111.346s Main at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:183) C 111.347s Main at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:560) C 111.347s Main at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1932) C 111.347s Main ******************************************************************************** C 111.347s Main Summary C 111.347s Main ******************************************************************************** C 111.347s Main [==========] 1 test ran. C 111.347s Main [ PASSED ] 0 tests. C 111.347s Main [ FAILED ] 1 test, listed below: C 111.347s Main [ FAILED ] org.chromium.chrome.browser.suggestions.SuggestionsBottomSheetTest#testContextMenu C 111.347s Main C 111.347s Main 1 FAILED TEST C 111.347s Main ******************************************************************************** Please use labels and text to provide additional information. Note: The SHA listed above is just a sample SHA this is failing on, not the root cause! The tests have been failing for several weeks before that SHA.
,
Sep 12 2017
I also get this on a bunch of activity tests, it seems to be because the native chrome.cr library takes too long to load. Doesn't seem to be an issue on the bots. Increasing the timeouts using the --timeout-scale flag is a local workaround.
,
Jan 31 2018
,
Mar 7 2018
Closing as likely moot. |
|||
►
Sign in to add a comment |
|||
Comment 1 Deleted