Skip to content

test: Update connection-monitoring-and-pooling specs #2555

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

Merged
merged 5 commits into from
Oct 1, 2020

Conversation

nbbeeken
Copy link
Contributor

Update connection-monitoring-and-pooling tests
ensuring ConnectionCreated proceed ConnectionReady events

NODE-2804

Note to reviewers

I have a spec sync script I suggest we bring in here, if anyone has a hesitation we can drop that.
There were a few formatting issues that made it to 3.6, the fixes are in here.

Copy link
Contributor

@reggi reggi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I like the update script 🤩

The only issue is that we may not want to pull master, I am usually cherry-picking files from a specific commit hash, or pulling all changes to a spec folder from a commit hash. I've never considered taking from master.

Copy link
Member

@mbroadst mbroadst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with a nit for the sync script

Update connection-monitoring-and-pooling tests
ensuring ConnectionCreated proceed ConnectionReady events

NODE-2804
@nbbeeken nbbeeken force-pushed the NODE-2804/create-before-ready-event branch from a5f5d49 to b014976 Compare September 30, 2020 14:10
@nbbeeken nbbeeken requested a review from reggi September 30, 2020 17:30
@nbbeeken
Copy link
Contributor Author

LGTM, I like the update script 🤩

The only issue is that we may not want to pull master, I am usually cherry-picking files from a specific commit hash, or pulling all changes to a spec folder from a commit hash. I've never considered taking from master.

@reggi PTAL at the update script (even better would be if you could give it a whirl for me). Should be able to support a specific git hash as an optional second argument.

curl -sL "https://github.com/mongodb/specifications/archive/master.zip" -o "$tmpdir/specs.zip"
unzip -d "$tmpdir" "$tmpdir/specs.zip" > /dev/null
mkdir -p "$spec_root/$1"
rsync -ah "$tmpdir/specifications-master/source/$1/tests/" "$spec_root/$1" --delete
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
rsync -ah "$tmpdir/specifications-master/source/$1/tests/" "$spec_root/$1" --delete
rsync -ah --exclude '*.rst' "$tmpdir/specifications-master/source/$1/tests/" "$spec_root/$1" --delete

@nbbeeken nbbeeken merged commit b70baf4 into 3.6 Oct 1, 2020
@nbbeeken nbbeeken deleted the NODE-2804/create-before-ready-event branch October 1, 2020 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants