Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Intermittent UI test failure - < SettingsAddonsTest. verifyAddonsCanBeUninstalled > #24843

Closed
AndiAJ opened this issue Apr 18, 2022 · 3 comments
Assignees
Labels
eng:disabled-test For any test that has been disabled eng:intermittent-test Evil test failures that only happen now-and-then and are a productivity killer eng:ui-test UI Tests

Comments

@AndiAJ
Copy link
Collaborator

AndiAJ commented Apr 18, 2022

Firebase Test Run: Firebase link

Stacktrace:

androidx.test.espresso.IdlingResourceTimeoutException: Wait for [javaClass] to become idle timed out
at dalvik.system.VMStack.getThreadStackTrace(Native Method)
at java.lang.Thread.getStackTrace(Thread.java:1538)
at androidx.test.espresso.base.DefaultFailureHandler.getUserFriendlyError(DefaultFailureHandler.java:16)
at androidx.test.espresso.base.DefaultFailureHandler.handle(DefaultFailureHandler.java:36)
at androidx.test.espresso.ViewInteraction.waitForAndHandleInteractionResults(ViewInteraction.java:106)
at androidx.test.espresso.ViewInteraction.check(ViewInteraction.java:31)
at org.mozilla.fenix.ui.robots.SettingsSubMenuAddonsManagerRobot$Transition.openDetailedMenuForAddon(SettingsSubMenuAddonsManagerRobot.kt:111)
at org.mozilla.fenix.ui.SettingsAddonsTest.verifyAddonsCanBeUninstalled(SettingsAddonsTest.kt:109)
at java.lang.reflect.Method.invoke(Native Method)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at androidx.test.internal.runner.junit4.statement.RunBefores.evaluate(RunBefores.java:80)
at androidx.test.internal.runner.junit4.statement.RunAfters.evaluate(RunAfters.java:61)
at androidx.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:531)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:56)
at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:395)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2145)

Build: 4/18

┆Issue is synchronized with this Jira Task

@AndiAJ AndiAJ added eng:intermittent-test Evil test failures that only happen now-and-then and are a productivity killer eng:ui-test UI Tests labels Apr 18, 2022
@github-actions github-actions bot added the needs:triage Issue needs triage label Apr 18, 2022
@AndiAJ AndiAJ removed the needs:triage Issue needs triage label Apr 18, 2022
@sv-ohorvath
Copy link
Contributor

Same issue as #24815 - addon failed to install

@sv-ohorvath sv-ohorvath self-assigned this Apr 29, 2022
Amejia481 added a commit to badboy/fenix that referenced this issue May 5, 2022
Amejia481 added a commit to badboy/fenix that referenced this issue May 5, 2022
mergify bot pushed a commit that referenced this issue May 5, 2022
@AndiAJ AndiAJ added the eng:disabled-test For any test that has been disabled label May 6, 2022
@AndiAJ
Copy link
Collaborator Author

AndiAJ commented May 6, 2022

Disabled in #25060

sv-ohorvath added a commit that referenced this issue Jun 14, 2022
…es in tests.

Retrying add-on installation if it fails.
sv-ohorvath added a commit that referenced this issue Jun 14, 2022
…es in tests.

Retrying add-on installation if it fails.
sv-ohorvath added a commit that referenced this issue Jun 14, 2022
…es in tests.

Retrying add-on installation if it fails.
sv-ohorvath added a commit that referenced this issue Jun 17, 2022
…es in tests.

Retrying add-on installation if it fails.
sv-ohorvath added a commit that referenced this issue Jun 17, 2022
…es in tests.

Retrying add-on installation if it fails.
mergify bot pushed a commit that referenced this issue Jun 21, 2022
…es in tests.

Retrying add-on installation if it fails.
@sv-ohorvath
Copy link
Contributor

Hopefully fixed in #25613

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
eng:disabled-test For any test that has been disabled eng:intermittent-test Evil test failures that only happen now-and-then and are a productivity killer eng:ui-test UI Tests
Projects
None yet
Development

No branches or pull requests

2 participants