test: resumability for change stream unified tests #3282
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
evergreen run |
nbbeeken
reviewed
Jun 2, 2022
nbbeeken
previously approved these changes
Jun 2, 2022
nbbeeken
added
the
Primary Review
nbbeeken
previously approved these changes
Jun 3, 2022
nbbeeken
added
Team Review
baileympearson
force-pushed
the
no-story-fix-resumability-unified-change-stream-tests
branch
from
b17136f to
e5fef5b
Compare
nbbeeken
approved these changes
Jun 3, 2022
nbbeeken
changed the title
nbbeeken
deleted the
no-story-fix-resumability-unified-change-stream-tests
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
What is changing?
This PR fixes resumabillity for change stream unified tests. It also deletes the legacy change stream tests, now that all the unified tests are running.
Is there new documentation needed for these changes?
No.
Double check the following
npm run check:lintscript<type>(NODE-xxxx)<!>: <description>