You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Sync tests on Github Actions appear a lot more flaky than they did on Jenkins. It is unclear exactly what the issue is. It could either be that the GHA network is just flaky or it could be our BAAS server test infrastructure.
But we should find a way to address it. It might be something as simple as just raising the connection timeout, but this needs to be investigated.
Below are just a few examples of the errors seen. The timeout is not associated with a single test:
https://github.com/realm/realm-kotlin/actions/runs/7561504211/job/20603264715
❌ realmQuery_subscribe_anonymousTwice[macos]
io.ktor.client.network.sockets.SocketTimeoutException: Socket timeout has expired [url=http://18.207.129.183:37397/api/admin/v3.0/auth/providers/local-userpass/login, socket_timeout=60000] ms
https://github.com/realm/realm-kotlin/runs/20531085620
❌ recoverOrDiscardUnsyncedChangesStrategyMode[macos]
io.realm.kotlin.mongodb.exceptions.ConnectionException: [Custom][CustomError(4000)] io.ktor.client.network.sockets.SocketTimeoutException: Socket timeout has expired [url=http://18.207.129.183:36091/api/client/v2.0/app/test-app-pbs-vnjxh/location, socket_timeout=60000] ms.
The text was updated successfully, but these errors were encountered:
Running Sync tests on Github Actions appear a lot more flaky than they did on Jenkins. It is unclear exactly what the issue is. It could either be that the GHA network is just flaky or it could be our BAAS server test infrastructure.
But we should find a way to address it. It might be something as simple as just raising the connection timeout, but this needs to be investigated.
Below are just a few examples of the errors seen. The timeout is not associated with a single test:
The text was updated successfully, but these errors were encountered: