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

test(NODE-3713): skip/fix failing evergreen tests #3069

Merged
merged 6 commits into from
Dec 17, 2021
Merged

test(NODE-3713): skip/fix failing evergreen tests #3069

merged 6 commits into from
Dec 17, 2021

Conversation

durran
Copy link
Member

@durran durran commented Dec 7, 2021

Description

Skips or fixes failing non Ubuntu evergreen tests

What is changing?

Skips failing tests on MacOS and Windows plus increases test run timeouts.

Notes

The failing client side encryption corpus tests I believe will be fixed by mongodb/libmongocrypt#225

KDC error messages updated for failing Kerberos tests.

Documentation Changes

No

What is the motivation for this change?

NODE-3713

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

https://spruce.mongodb.com/version/61bc8d837742ae2cc78c16e9/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

@durran durran force-pushed the NODE-3713 branch 3 times, most recently from ac34bd4 to 0af06ca Compare December 13, 2021 17:58
@durran durran changed the title test(NODE-3713): skip failing evergreen tests test(NODE-3713): skip/fix failing evergreen tests Dec 13, 2021
@durran durran force-pushed the NODE-3713 branch 6 times, most recently from 5ecc331 to eb0351d Compare December 14, 2021 17:30
@dariakp dariakp added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Dec 14, 2021
@dariakp dariakp self-requested a review December 14, 2021 19:29
Copy link
Contributor

@dariakp dariakp left a comment

Choose a reason for hiding this comment

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

I went ahead and marked the lines where we need unskip tickets (don't necessarily need a separate ticket for each one, but just something that's actually in our backlog in the Testing Improvements epic to address in the future)

test/functional/connections_stepdown.test.js Outdated Show resolved Hide resolved
test/functional/cursorstream.test.js Outdated Show resolved Hide resolved
test/functional/examples/change_streams.test.js Outdated Show resolved Hide resolved
test/functional/find.test.js Show resolved Hide resolved
test/functional/unit-sdam/monitoring.test.js Show resolved Hide resolved
test/functional/write_concern.test.js Outdated Show resolved Hide resolved
@@ -71,7 +71,7 @@ describe('Kerberos', function () {
client.connect(function (err) {
expect(err).to.exist;
expect(err.message).to.match(
/(Error from KDC: LOOKING_UP_SERVER)|(not found in Kerberos database)/
/(Error from KDC: LOOKING_UP_SERVER)|(not found in Kerberos database)|(UNKNOWN_SERVER)/
Copy link
Contributor

Choose a reason for hiding this comment

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

This is interesting - just curious how/when/why this manifested?

Copy link
Member Author

Choose a reason for hiding this comment

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

It started happening last week and only on MacOS. I'm trying to pin down the root cause at the moment but Kerberos knowledge is obviously not one of my strengths.

Copy link
Contributor

@dariakp dariakp left a comment

Choose a reason for hiding this comment

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

For the tests that link to a MacOS skip, let's just skip them conditionally on the OS instead of always skipping

@durran
Copy link
Member Author

durran commented Dec 17, 2021

For the tests that link to a MacOS skip, let's just skip them conditionally on the OS instead of always skipping

This has been added now.

@durran durran force-pushed the NODE-3713 branch 2 times, most recently from 315da13 to 23f9155 Compare December 17, 2021 05:11
@dariakp dariakp added Team Review Needs review from team and removed Primary Review In Review with primary reviewer, not yet ready for team's eyes labels Dec 17, 2021
Copy link
Contributor

@dariakp dariakp left a comment

Choose a reason for hiding this comment

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

Just wanted to double check about these 3 tests:

test/functional/find.test.js Show resolved Hide resolved
test/functional/unit-sdam/monitoring.test.js Show resolved Hide resolved
@dariakp dariakp merged commit 8a3bab7 into main Dec 17, 2021
@dariakp dariakp deleted the NODE-3713 branch December 17, 2021 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team Review Needs review from team
Projects
None yet
2 participants