[no-issue]: Reduce flakiness in sync queue related tests #4170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the change to making the ChangeHandlers run in a transaction, these sync queue related tests have all become a bit more flaky (eg. here, and here). They have previously been relying purely on timing at points, which isn't really all that safe. I've added a bunch of
await database.waitForAllChangeHandlers();
calls in places where they seemed necessary, which should halt the test execution until the change transaction is complete.