-
Notifications
You must be signed in to change notification settings - Fork 1.8k
test: new test runner changes from lb support #2901
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
Conversation
dariakp
left a comment
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.
Just a few outstanding questions/concerns here
| // TODO: NodeJS Driver has extra events | ||
| // expect(actual).to.have.lengthOf(expected.length); | ||
| if (actual.length !== expected.length) { | ||
| // const actualNames = actual.map(a => a.constructor.name); |
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.
this seems to be an empty code block
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.
Relevant convo over on the bigger PR: #2742 (comment)
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.
@nbbeeken Thanks! still think that we should maybe remove the if block and the code that attempts to do things and add a comment in the code summarizing this:
It was intentional as the Node driver does not execute a killCursors after a getMore has errored, which causes the absence of the killCursors events in some cases. I could not find anywhere so far in the specs that states an errored getMore requires an immediate killCursors afterwards, and all the driver does in this case is cleanup the cursor (but not explicitly close() it).
(maybe even file a ticket to explore this further, since if we know exactly what's out of the ordinary, we may be able to filter explicitly those cases out)
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.
This check is now back and asserting the event lengths, so no comment needed.
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.
It looks like some of the new snapshot tests are failing now with that check, I don't think you need to take care of it here because I need to sort out those tests anyway, but if you could add them to the skip list, that would allow the pipeline to stay green on main
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.
snapshot-sessions-unsupported-ops
- Server returns an error on findOneAndUpdate with snapshot
- Server returns an error on deleteOne with snapshot
- Server returns an error on updateOne with snapshot
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've skipped the one failing test now.
dariakp
left a comment
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.
Thank you very much!
nbbeeken
left a comment
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.
LGTM
emadum
left a comment
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.
LGTM 👍
* test: new test runner changes from lb support * test: refactoring unified runner * test: bring back unified event length check * test: run txn tests in manual lb tests * test: skip failing snapshot test and refactor matchers * test: remove lb manual test * test: skip other failed tests
No description provided.