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

Flaky test: io.realm.kotlin.test.mongodb.jvm.PlatformNetworkingTests.syncRoundTrip_coreNetworking #1819

Open
rorbech opened this issue Aug 13, 2024 · 1 comment

Comments

@rorbech
Copy link
Contributor

rorbech commented Aug 13, 2024

There seem to be something related to platform networking that isn't torn properly down. When running tests on CI the Sync JVM Linux tests sometimes fails to pass on the Flaky test: io.realm.kotlin.test.mongodb.jvm.PlatformNetworkingTests.syncRoundTrip_coreNetworking due to some callbacks to the a websocket-transport client.

2024-08-13T08:49:51.1361363Z     2024-Aug-13 08:49:51,116 DEBUG: [REALM] [SDK] [Websocket-210459023] init
2024-08-13T08:49:51.3303847Z     2024-Aug-13 08:49:51,241 DEBUG: [REALM] [SDK] [Websocket-210459023] onOpen websocket http://100.27.1.167:36319/api/client/v2.0/app/test-app-flx-ugksndu/realm-sync?baas_at=***
2024-08-13T08:49:51.3305415Z     2024-Aug-13 08:49:51,241 DEBUG: [REALM] [SDK] [Websocket-210459023] onClosing code = 1011 reason = error isClosed = false observerIsClosed = false

Assuming that this is something that it unexpectedly cached somewhere in app context in the sync client as we should be closing and terminating sync from the SDK side.

Seen in https://github.com/realm/realm-kotlin/actions/runs/10365026696/job/28695503175

Copy link

sync-by-unito bot commented Aug 13, 2024

➤ PM Bot commented:

Jira ticket: RKOTLIN-1119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant