New issue
Advanced search Search tips

Issue 921062 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

org.chromium.chrome.browser.autofill.AutofillPopupWithKeyboardTest#testShowAutofillPopupAndKeyboardimultaneously is flaky

Project Member Reported by adithyas@chromium.org, Jan 11

Issue description

Test fails with following stack trace:

java.lang.AssertionError: Autofill Popup anchor view was never added.
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.chromium.content_public.browser.test.util.CriteriaHelper.pollInstrumentationThread(CriteriaHelper.java:92)
	at org.chromium.content_public.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:171)
	at org.chromium.content_public.browser.test.util.CriteriaHelper.pollUiThread(CriteriaHelper.java:193)
	at org.chromium.chrome.browser.autofill.AutofillPopupWithKeyboardTest.testShowAutofillPopupAndKeyboardimultaneously(AutofillPopupWithKeyboardTest.java:112)
	at java.lang.reflect.Method.invoke(Method.java)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.chromium.base.test.ScreenshotOnFailureStatement.evaluate(ScreenshotOnFailureStatement.java:41)
	at org.chromium.chrome.test.ChromeActivityTestRule$1.evaluate(ChromeActivityTestRule.java:129)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at android.support.test.internal.statement.UiThreadStatement.evaluate(UiThreadStatement.java:55)
	at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:270)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:237)
	at org.chromium.base.test.BaseJUnit4ClassRunner.runChild(BaseJUnit4ClassRunner.java:48)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.chromium.base.test.CommitSharedPreferencesTestRule$1.evaluate(CommitSharedPreferencesTestRule.java:20)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.chromium.base.test.BaseJUnit4ClassRunner.run(BaseJUnit4ClassRunner.java:220)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
	at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:59)
	at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:262)
	at org.chromium.base.test.BaseChromiumAndroidJUnitRunner.onStart(BaseChromiumAndroidJUnitRunner.java:128)
	at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1879)

Flakiness dashboard: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=chrome_public_test_apk&tests=org.chromium.chrome.browser.autofill.AutofillPopupWithKeyboardTest%23testShowAutofillPopupAndKeyboardimultaneously

Example failing build: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Android%20CFI/4231
 
Culprit is not obvious, so I'm going to disable the test for now.
Cc: ftirelo@chromium.org
Owner: fhorschig@chromium.org
fhorschig@chromium.org Is this related to your work? If so could you please take a look? Thanks!
Project Member

Comment 3 by bugdroid1@chromium.org, Jan 11

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

commit 70c0f755d372b575c224f09c77f3f39a17ef6d7f
Author: Adithya Srinivasan <adithyas@chromium.org>
Date: Fri Jan 11 16:55:50 2019

Disable testShowAutofillPopupAndKeyboardSimulatenously

Tbr: sebsg@chromium.org
No-Try: true
Bug: 921062
Change-Id: Ic9699d7c3a2350e4969730288ae1ffae47917f4b
Reviewed-on: https://chromium-review.googlesource.com/c/1407091
Reviewed-by: Adithya Srinivasan <adithyas@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#622033}
[modify] https://crrev.com/70c0f755d372b575c224f09c77f3f39a17ef6d7f/chrome/android/javatests/src/org/chromium/chrome/browser/autofill/AutofillPopupWithKeyboardTest.java

Cc: -ftirelo@chromium.org
Owner: ftirelo@chromium.org
Not sure who is familiar with the autofill tests, but Fabio might know.

I mostly know about tests in autofill.keyboard_accessory.* which are (surprisingly) quite different from autofill.* tests ;)
Labels: -Sheriff-Chromium
Test disabled and assigned an owner --> Taking out of sheriff queue.
Cc: ftirelo@chromium.org
Owner: tmartino@chromium.org
Hi Tommy. Since you've working on the Autofill dropdown on Android, can you take a look at this flaky test?

Sign in to add a comment