-
Notifications
You must be signed in to change notification settings - Fork 1.8k
test(NODE-5317): use new evergreen scripts #3669
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
a72240e
to
4c280f3
Compare
${MONGODB_BINARIES}/mongo --nodb setup.js aws_e2e_ecs.js | ||
export MONGODB_BINARIES="${MONGODB_BINARIES}"; | ||
export PROJECT_DIRECTORY=$PROJECT_DIRECTORY; | ||
python aws_tester.py ecs |
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 will fail our first AWS test that checks that no auth credentials in the URI will fail. It actually connects successfully because the mongod is started without enforcing access control.
.evergreen/config.yml
Outdated
# fix issue with `TestData` in SERVER-46340 | ||
sed -i '1s+^+TestData = {};\n+' $AUTH_AWS_DIR/lib/ecs_hosted_test.js | ||
# sed -i '1s+^+TestData = {};\n+' $AUTH_AWS_DIR/lib/ecs_hosted_test.js |
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.
Tests are passing with this code commented out - should this be removed entirely?
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 removed.
evergreen retry |
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.
failing tests are unrelated to the changes in this PR
Description
Updates the driver to use the new AWS auth Evergreen scripts.
What is changing?
Updates the driver to use mongodb-labs/drivers-evergreen-tools#306
NOTE The failure scenario is removed from the AWS tests as the servers that are set up in the scripts have access control disabled, which means connecting without auth will succeed, rendering that test as a failure. The auth prose tests require no failure case, so this is now removed.
Is there new documentation needed for these changes?
None
What is the motivation for this change?
DRIVERS-2328
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript