Skip to content

chore: skip integration tests for Windows too in Evergreen #227

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 1 commit into from
Aug 8, 2025

Conversation

addaleax
Copy link
Contributor

@addaleax addaleax commented Aug 7, 2025

These seem to have started to fail recently too, without changes to the code itself (i.e. possibly only because of infrastructure or external dependency changes such as Chrome updates).

This is still covered in Github Actions.

These seem to have started to fail recently too, without changes to the
code itself (i.e. possibly only because of infrastructure or external
dependency changes such as Chrome updates).
Copy link

@kmruiz kmruiz left a comment

Choose a reason for hiding this comment

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

Should we remove all these tests in Evergreen and only keep GHA?

@addaleax
Copy link
Contributor Author

addaleax commented Aug 8, 2025

@kmruiz I guess that would be an option ... I think it's not a bad thing in general to test that this plugin works in the environments where we also test e.g. Compass itself, but yeah, we can talk about it when triaging MONGOSH-2335 I'd say?

@addaleax addaleax merged commit 8fbf605 into main Aug 8, 2025
21 checks passed
@addaleax addaleax deleted the windows-skip-okta branch August 8, 2025 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants