[release/6.0-staging][android] Bump to win 11 helix queue - #107450
Merged
Merged
Conversation
Member
Author
|
@carlossanlop infra-only change, marking as servicing-approved. |
Contributor
|
Tagging subscribers to this area: @directhex, @matouskozak |
steveisok
self-requested a review
September 6, 2024 13:04
steveisok
approved these changes
Sep 6, 2024
carlossanlop
approved these changes
Sep 6, 2024
Member
Author
|
/ba-g failures are not related to Android so the changes can't have affected them. |
This was referenced Sep 11, 2024
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
Backport of #96139 to release/6.0-staging.
Same as #96634 just for the 6.0 branch. Dnceng would like to remove this old Helix queue.
Customer Impact
None, this is an infrastructure change
Testing
CI testing.
Risk
None.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging, notrelease/X.0.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.