New issue
Advanced search Search tips

Issue 726293 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

SystemWebViewShellLayoutTest (CTS) failing on chromium.android/Android WebView M (dbg)

Project Member Reported by dgn@chromium.org, May 25 2017

Issue description

SystemWebViewShellLayoutTest failing on chromium.android/Android WebView M (dbg)

Builders failed on: 
- Android WebView M (dbg): 
  https://build.chromium.org/p/chromium.android/builders/Android%20WebView%20M%20%28dbg%29


[FAIL] android.webkit.cts.WebSettingsTest#testAccessJavaScriptCanOpenWindowsAutomatically:
junit.framework.AssertionFailedError: unexpected timeout
	at junit.framework.Assert.fail(Assert.java:50)
	at android.cts.util.PollingCheck.run(PollingCheck.java:56)
	at android.webkit.cts.WebSettingsTest.testAccessJavaScriptCanOpenWindowsAutomatically(WebSettingsTest.java:419)
	at java.lang.reflect.Method.invoke(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 junit.framework.TestCase.runBare(TestCase.java:134)
	at junit.framework.TestResult$1.protect(TestResult.java:115)
	at android.support.test.internal.runner.junit3.AndroidTestResult.runProtected(AndroidTestResult.java:77)
	at junit.framework.TestResult.run(TestResult.java:118)
	at android.support.test.internal.runner.junit3.AndroidTestResult.run(AndroidTestResult.java:55)
	at junit.framework.TestCase.run(TestCase.java:124)
	at android.support.test.internal.runner.junit3.NonLeakyTestSuite$NonLeakyTest.run(NonLeakyTestSuite.java:63)
	at junit.framework.TestSuite.runTest(TestSuite.java:243)
	at junit.framework.TestSuite.run(TestSuite.java:238)
	at android.support.test.internal.runner.junit3.DelegatingTestSuite.run(DelegatingTestSuite.java:103)
	at android.support.test.internal.runner.junit3.AndroidTestSuite.run(AndroidTestSuite.java:69)
	at android.support.test.internal.runner.junit3.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:24)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:136)
	at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:54)
	at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:228)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879)

tobiasjs@ Could you please help triage?
 
Owner: jochen@chromium.org
Jochen, I think this might be your change: https://chromium-review.googlesource.com/512347 - the first failing run is https://build.chromium.org/p/chromium.android/builders/Android%20WebView%20M%20%28dbg%29/builds/5248, which contains your change. Could you please take a look?

Comment 2 by jochen@chromium.org, May 25 2017

Cc: torne@chromium.org
I can't even find that test in codesearch :/

how do I run it?

Comment 3 by torne@chromium.org, May 25 2017

Isn't this the same CTS test that we talked about (and you fixed your CL to deal with) the other day?

Comment 4 by jochen@chromium.org, May 26 2017

Mergedinto: 725115
Status: Duplicate (was: Available)

Comment 5 by jochen@chromium.org, May 26 2017

Turns out I didn't read the test name carefully :/

the cts test is slightly different from the one checked into chromium..

Sign in to add a comment