-
Notifications
You must be signed in to change notification settings - Fork 459
Migrate server 8.0+ tasks to windows-2022-latest #2197
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
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 migration revealed various task failures on Windows, but work to address these failures are deferred to followup PRs due to being out-of-scope for this migration PR.
kevinAlbs
left a comment
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.
Also recommend updating tasks in the legacy config relying using windows-vsCurrent-large that failing on the linked Evergreen patch
|
Updated the legacy config as follows:
|
kevinAlbs
left a comment
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.
LGTM with remaining tasks migrated.
Resolve ongoing task failures against latest server version on Windows due to SERVER-116018 by migrating all 8.0+ tasks from
windows-vsCurrent(Windows 2019) towindows-2022-latest(Windows 2022). Note only Visual Studio 2022 is provided onwindows-2022-latest.AllCyrus SASL was dropped on Windows in CDRIVER-5514.ENABLE_SASL=CYRUStasks onwindows-2022-latestwill continue to fail until DEVPROD-26205 is resolved (missing the Cyrus SASL library).