-
Notifications
You must be signed in to change notification settings - Fork 784
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
Write range sync tests in external event-driven form #6618
Conversation
Nice! Looks clean and easy to read 👍 |
This test is failing in CI after switching to async, but can't reproduce locally |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I managed to reproduce the failing test locally, not sure why it was passing before 🤔 We do need it in this case I think, so we might have uncovered a lurking issue - adding a mock execution layer fixed it.
The other changes look good, thanks!
@mergify queue |
🛑 The pull request has been removed from the queue
|
@mergify dequeue |
This pull request has been removed from the queue for the following reason: Pull request #6618 has been dequeued by a You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. If you want to requeue this pull request, you need to post a comment with the text: |
✅ The pull request has been removed from the queue
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyThe followup |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 1c5be34 |
Issue Addressed
Re-write existing range sync tests into an event-driven format to accommodate the refactor introduced in
This format was introduced in
and does not make assumptions about internal functions, it treats sync as a black box inputting actual events used in production.
Note: I've removed the generics used in range sync since now we don't unit test directly