-
Notifications
You must be signed in to change notification settings - Fork 6
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
Reenable disconnect failed resume faults #947
Conversation
android-test-common/src/main/java/com/ably/tracking/test/android/common/Faults.kt
Outdated
Show resolved
Hide resolved
From my testing @ikbalkaya, it should also be safe to reenable |
@AndyTWF (I mean @jaley 😄 )In my local, only one passes unfortunately. The one with |
OK, no worries. Let's leave it disabled if you're seeing problems and just prioritise getting the ably-java bump landed |
@jaley I realized I had this test run without changes also from main - Now I can confirm that both test pass and I reenabled the EnterUnresponsive fault as well now. I will wait for CI checks pass and merge the changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
This PR does three things
DisconnectFailedWithResume
EnterUnresponsive
Closes Adding a trackable stalls forever if presence.enter() is interrupted by a disconnection #896