Skip to content
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

fix: boron node version test failures #2747

Merged
merged 2 commits into from
Mar 5, 2021
Merged

fix: boron node version test failures #2747

merged 2 commits into from
Mar 5, 2021

Conversation

nbbeeken
Copy link
Contributor

@nbbeeken nbbeeken commented Mar 3, 2021

Some of the deprecation warnings are formatted a little different in node boron (v6), updated the tests to account for that.

Copy link
Contributor

@emadum emadum left a comment

Choose a reason for hiding this comment

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

One question but LGTM!

@@ -1264,7 +1264,7 @@ describe('Indexes', function() {
metadata: {
requires: {
topology: ['single', 'replicaset', 'sharded', 'ssl', 'heap', 'wiredtiger'],
mongodb: '>=3.0.0'
mongodb: '>=3.0.0 <=4.8.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you have more context on what is going on with this test? I've seen it fail on some of my CI runs against latest as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Looks like version 4.9.0-alpha5-148-g3a70e27 now returns code 86 instead of 85 for this use case, figured we might as well keep the test running on versions prior to that. I went with capping it at the minor version just to be sure we don't run into this on newer versions

This was referenced Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants