-
Notifications
You must be signed in to change notification settings - Fork 344
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
Updated WindowsAppSDK-RunTestsInPipeline-Job.yml #3996
Conversation
/azp run |
"21H2" is both Win10 and Win11. You're referring to the Win11 21H2 (aka SV1)? https://en.wikipedia.org/wiki/Windows_10_version_history https://en.wikipedia.org/wiki/Windows_11_version_history
Zero loss if you count supported releases. Win11 21H2 Home/Pro supported ended last month (Oct'2023). Win11 21H2 Enterprise plus Win11 22H2 are still supported and their test pipelines are still humming so all good |
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
* Remove corefresh from tests * also remove Server22_DC_arm64fre
* Remove corefresh from tests * also remove Server22_DC_arm64fre
Pipeline runs seem to be failing consistently due to failure to acquire a co_refresh VM for testing.
OSGWiki says cobalt Home/Pro SKUs hit End of Support on Oct 10, 2023. That appears to explain it.
Skipping testing on co_refresh to unblock pipeline runs. Cobalt is 21h2. We are still testing the Windows.11.Enterprise.MultiSession.21h2 OS image which has another year before end of support, so we don't lose much test coverage with this change.