Remove WS2025 from CIs #2483
Merged
Remove WS2025 from CIs #2483
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
There are known regressions in Ws2025 networking which is causing several sig-windows nightlies to fail as well. Remove Ws2025 from CIs like we did in containerd for the interim Signed-off-by: Kirtana Ashok <kiashok@microsoft.com>
ambarve
approved these changes
Jul 17, 2025
anmaxvl
approved these changes
Jul 17, 2025
|
@kiashok is this "known regressions" publicly documented somewhere and can we expect that to be fixed by Windows updates? I would like to understand more about this as we are planning migrate our containers to W2025. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
There are known regressions in Ws2025 networking
which is causing several sig-windows nightlies to fail as well.
Remove Ws2025 from CIs like we did in containerd for the interim