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

Flakey Realtime test channel_resume_lost_continuity in RealtimeChannelTest #899

Open
QuintinWillison opened this issue Jan 12, 2023 · 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

Seen here at 3d252b6:

-> Test channel_resume_lost_continuity[binary_protocol](io.ably.lib.test.realtime.RealtimeChannelTest)

io.ably.lib.test.realtime.RealtimeSuite > io.ably.lib.test.realtime.RealtimeChannelTest.channel_resume_lost_continuity[binary_protocol] FAILED
    java.lang.AssertionError: Verify channel was attached expected:<false> but was:<true>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:834)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at io.ably.lib.test.realtime.RealtimeChannelTest.channel_resume_lost_continuity(RealtimeChannelTest.java:1625)

More detail from build report:

java.lang.AssertionError: Verify channel was attached expected:<false> but was:<true>
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at io.ably.lib.test.realtime.RealtimeChannelTest.channel_resume_lost_continuity(RealtimeChannelTest.java:1625)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	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.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.lang.Thread.run(Thread.java:829)
@QuintinWillison QuintinWillison added the failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug. label Jan 12, 2023
@sync-by-unito
Copy link

sync-by-unito bot commented Jan 12, 2023

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3234

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