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.

Sign up for GitHub

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

Jump to bottom

Fix flaky static queries tests #3560

Closed
papafe opened this issue Mar 21, 2024 · 2 comments · May be fixed by #3595
Closed

Fix flaky static queries tests #3560

papafe opened this issue Mar 21, 2024 · 2 comments · May be fixed by #3595
Assignees
@papafe

Comments

@papafe
Copy link
Contributor

papafe commented Mar 21, 2024 •
edited
Loading

We should fix flaky static queries tests, for example in:

It seems most of the time it's the tests RealmObjectAPI_RealmValueLinks_AtlasToRealm and RealmObjectAPI_Links_AtlasToRealm that are giving issues. I think this could be due to some timing issues, for example if objects are created but the properties are not set yet, or if clearing the collection at the beginning is not yet propagated to realm before continuing.
@sync-by-unito Sync by Unito
Copy link

sync-by-unito bot commented Mar 21, 2024

➤ PM Bot commented:

Jira ticket: RNET-1126

@papafe
Copy link
Contributor Author

papafe commented Mar 21, 2024

I think that here we have two possibilities:

  • Retry the tests with the Retry attribute
  • We make much larger use of the WaitForEvent, WaitForCondition methods, almost substituting the assertion with the timeouts of those methods

@papafe papafe mentioned this issue May 3, 2024
Draft
@papafe papafe closed this as completed Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@papafe papafe

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

RNET-1126: Fix flaky tests on CI realm/realm-dotnet
1 participant
@papafe