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

waitForInitialData_resilientInCaseOfRetriesAsync fails #5373

Closed
cmelchior opened this issue Oct 3, 2017 · 4 comments
Closed

waitForInitialData_resilientInCaseOfRetriesAsync fails #5373

cmelchior opened this issue Oct 3, 2017 · 4 comments
Labels
Milestone

Comments

@cmelchior
Copy link
Contributor

cmelchior commented Oct 3, 2017

SyncedRealmTests#waitForInitialData_resilientInCaseOfRetriesAsync fails somewhat consistently on both CI and me locally.

I have only been able to reproduce it when running all tests in SyncedRealmTests, so perhaps it is interactions with previous tests, although given the error that is kinda weird.

Log from a failed run is:

10-03 08:37:29.034 4699-4740/io.realm.test A/REALM_JNI: An exception has been thrown on the sync client thread:
                                                        open("/data/data/io.realm.test/files/realm-object-server/d6769925c090ed605dd6235c9ad74a80/d6769925c090ed605dd6235c9ad74a80/tests.management/access_control.write.mx") failed: No such file or directory
10-03 08:37:29.035 4699-4740/io.realm.test E/AndroidRuntime: FATAL EXCEPTION: Thread-7
                                                             Process: io.realm.test, PID: 4699
                                                             io.realm.exceptions.RealmError: An exception has been thrown on the sync client thread:
                                                             open("/data/data/io.realm.test/files/realm-object-server/d6769925c090ed605dd6235c9ad74a80/d6769925c090ed605dd6235c9ad74a80/tests.management/access_control.write.mx") failed: No such file or directory
@cmelchior cmelchior added the T-Bug label Oct 3, 2017
@cmelchior cmelchior added this to the 4.0.0 milestone Oct 3, 2017
@beeender
Copy link
Contributor

beeender commented Oct 3, 2017

open("/data/data/io.realm.test/files/realm-object-server/d6769925c090ed605dd6235c9ad74a80/d6769925c090ed605dd6235c9ad74a80/tests.management/access_control.write.mx") failed: No such file or directory

normally this caused by the test is finished, so we delete realm + remove the temp dir. But the realm instance on the sync client has not been closed.

@beeender
Copy link
Contributor

beeender commented Oct 3, 2017

with the new core API, we can make the deleteRealm() process safe which could also throw in tearDown() when deleteRealm() called.

@beeender
Copy link
Contributor

beeender commented Oct 26, 2017

OK, this test is not going to work because of #5416
deleteRealm will always throw in the executor service because of the Realm instance on the sync client thread is not closed.

@sync-by-unito
Copy link

sync-by-unito bot commented Dec 15, 2021

➤ Brian Munkholm commented:

Closing as this is related to Legacy sync

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants