Downgrade windows CI from 2022 to 2019 (fixes single test fail in CI) #865
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## develop #865 +/- ##
========================================
Coverage 88.69% 88.69%
========================================
Files 116 116
Lines 9440 9440
========================================
Hits 8373 8373
Misses 1067 1067 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
Works around #862 |
garrettwrong
changed the title
j-c-c
approved these changes
Feb 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Try windows server 2019 instead of latest (2022).Please disregard this PR. I'm just triggering the CI to see if this has the same failed test as windows 2022.If it fails this PR will be removed. Succeeds, I will edit this message.CI is reporting success using Win2019. I would like to merge this patch. Will leave issue open so we can revisit what is unhappy in Windows Server 2022 at a later date.