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

Investigate failures in test case RealtimeClientTests test__039__RealtimeClient__Auth_authorize_should_upgrade_the_connection_with_current_token__when_the_connection_is_in_the_DISCONNECTED_state_when_auth_authorize_is_called__after_obtaining_a_token_the_library_should_move_to_the_CONNECTING_state_and_initiate_a_connection_attempt_using_the_new_token (c2b81ea2-d06c-41a7-b217-36a144da77e5) #1338

Open
lawrence-forooghian opened this issue Apr 7, 2022 · 0 comments
Assignees
Labels
failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.

Comments

@lawrence-forooghian
Copy link
Collaborator

lawrence-forooghian commented Apr 7, 2022

https://test-observability.herokuapp.com/repos/ably/ably-cocoa/test_cases/c2b81ea2-d06c-41a7-b217-36a144da77e5

RealtimeClientTests.test__039__RealtimeClient__Auth_authorize_should_upgrade_the_connection_with_current_token__when_the_connection_is_in_the_DISCONNECTED_state_when_auth_authorize_is_called__after_obtaining_a_token_the_library_should_move_to_the_CONNECTING_state_and_initiate_a_connection_attempt_using_the_new_token

Split from #1330.

┆Issue is synchronized with this Jira Task by Unito

@lawrence-forooghian lawrence-forooghian added failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug. test-stability labels Apr 7, 2022
@maratal maratal self-assigned this May 2, 2022
@lawrence-forooghian lawrence-forooghian self-assigned this Aug 24, 2022
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

3 participants