Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore failing test NotActivated_on_CalledActivate_with_DeviceToken for RSH3a2a #739

Open
QuintinWillison opened this issue Jan 19, 2022 · 1 comment
Labels
failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.

Comments

@QuintinWillison
Copy link
Contributor

QuintinWillison commented Jan 19, 2022

We're consistently getting:

org.junit.runners.model.TestTimedOutException: test timed out after 300000 milliseconds
at java.lang.Object.wait(Native Method)
at io.ably.lib.test.common.Helpers$AsyncWaiter.waitFor(Helpers.java:775)
at io.ably.lib.test.android.AndroidPushTest$1TestCase.run(AndroidPushTest.java:584)
at io.ably.lib.test.util.TestCases$1.apply(TestCases.java:28)
at io.ably.lib.test.util.TestCases$1.apply(TestCases.java:24)
at io.ably.lib.test.common.Helpers.expectedError(Helpers.java:77)
at io.ably.lib.test.util.TestCases.run(TestCases.java:24)
at io.ably.lib.test.android.AndroidPushTest.NotActivated_on_CalledActivate_with_DeviceToken(AndroidPushTest.java:695)
at java.lang.reflect.Method.invoke(Native Method)
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:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.lang.Thread.run(Thread.java:761)

┆Issue is synchronized with this Jira Bug by Unito

@QuintinWillison QuintinWillison added the failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug. label Jan 19, 2022
@QuintinWillison QuintinWillison changed the title Restore failing test NotActivated_on_CalledActivate_with_DeviceToken Restore failing test NotActivated_on_CalledActivate_with_DeviceToken for RSH3a2a Jan 19, 2022
@QuintinWillison
Copy link
Contributor Author

Disabled in #738

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.
Development

No branches or pull requests

1 participant