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

Issue 663406 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Left Chrome team
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

LauncherActivityTest#testDoesNotCrashWithBadParcel failing on some devices

Reported by kra...@amazon.com, Nov 8 2016

Issue description

Version: Tip of master
OS: Android

What steps will reproduce the problem?
(1) Run LauncherActivityTest#testDoesNotCrashWithBadParcel on a
multiple generations old device that needs more time to launch the Activity
(e.g. 2nd generation Kindle Fire)

What is the expected output?
The test passes 10/10

What do you see instead?
I   31.642s Main  FINISHED TRY #1/1
I   31.642s Main  1 failed tests remain.
C   31.643s Main  ********************************************************************************
C   31.643s Main  Detailed Logs
C   31.643s Main  ********************************************************************************
C   31.643s Main  [FAIL] org.chromium.chrome.browser.document.LauncherActivityTest#testDoesNotCrashWithBadParcel:
C   31.643s Main  junit.framework.AssertionFailedError: ChromeLauncherActivity did not start Chrome
C   31.643s Main  	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:74)
C   31.643s Main  	at org.chromium.content.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:89)
C   31.643s Main  	at org.chromium.chrome.browser.document.LauncherActivityTest.tryLaunchingChrome(LauncherActivityTest.java:95)
C   31.643s Main  	at org.chromium.chrome.browser.document.LauncherActivityTest.testDoesNotCrashWithBadParcel(LauncherActivityTest.java:75)
C   31.644s Main  	at java.lang.reflect.Method.invokeNative(Native Method)
C   31.644s Main  	at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
C   31.644s Main  	at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
C   31.644s Main  	at android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTestCase2.java:186)
C   31.644s Main  	at org.chromium.chrome.test.ChromeActivityTestCaseBase.runTest(ChromeActivityTestCaseBase.java:726)
C   31.644s Main  	at org.chromium.base.test.BaseTestResult.runParameterized(BaseTestResult.java:161)
C   31.644s Main  	at org.chromium.base.test.BaseTestResult.run(BaseTestResult.java:124)
C   31.644s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
C   31.644s Main  	at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
C   31.644s Main  	at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:537)
C   31.644s Main  	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1551)
C   31.644s Main  ********************************************************************************
C   31.644s Main  Summary
C   31.645s Main  ********************************************************************************
C   31.645s Main  [==========] 1 test ran.
C   31.645s Main  [  PASSED  ] 0 tests.
C   31.645s Main  [  FAILED  ] 1 test, listed below:
C   31.645s Main  [  FAILED  ] org.chromium.chrome.browser.document.LauncherActivityTest#testDoesNotCrashWithBadParcel
C   31.645s Main
C   31.645s Main  1 FAILED TEST
C   31.645s Main  ********************************************************************************

Please use labels and text to provide additional information.
Fails 5/5 with the default timeout
Fails 5/5 with a timeout of 5 seconds
Fails 1/7 with a timeout of 10 seconds
Fails 0/20 with a timeout of 15 seconds
 
Project Member

Comment 1 by bugdroid1@chromium.org, Nov 9 2016

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

commit 6573d11c1c8f0e9805257276d9b82687c95e1d7d
Author: kraush <kraush@amazon.com>
Date: Wed Nov 09 16:20:25 2016

Increase timeout of LauncherActivityTest

Increase the timeout of LauncherActivityTest
to support devices where Activity startup takes
more time.

BUG= 663406 

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

[modify] https://crrev.com/6573d11c1c8f0e9805257276d9b82687c95e1d7d/chrome/android/javatests/src/org/chromium/chrome/browser/document/LauncherActivityTest.java

Comment 2 by ajha@chromium.org, Dec 7 2016

Labels: OS-Android

Comment 3 by cmasso@google.com, Feb 14 2018

Cc: yus...@chromium.org
Components: Tests>Fails
Owner: mariakho...@chromium.org
Status: Assigned (was: Untriaged)
Maria, is this fixed?
Status: Fixed (was: Assigned)
Yep this test looks healthy.

Sign in to add a comment