-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
chore(NODE-3719,NODE-3883): identify causal consistency spec tests #3112
chore(NODE-3719,NODE-3883): identify causal consistency spec tests #3112
Conversation
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.
Open question
test/integration/causal-consistency/causal_consistency.prose.test.js
Outdated
Show resolved
Hide resolved
888fda8
to
36bfe7f
Compare
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, looks like we captured everything. One Q that we could add to the follow up ticket
{ | ||
metadata: { | ||
requires: { topology: ['replicaset', 'sharded'] }, | ||
// Skipping session leak tests b/c these are explicit sessions |
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 is interesting, I would think this test still clean up the sessions it creates
Description
NODE-3719, NODE-3883
What is changing?
Identifying implemented and missing causal consistency spec tests; spec also says we should run on sharded topologies, not just replica set, so I expanded the required topology list.
Is there new documentation needed for these changes?
N/A
What is the motivation for this change?
Spec compliance audit
Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>