[release/7.0] Update arm queues #81712
Conversation
|
Tagging subscribers to this area: @hoyosjs Issue DetailsUpdating to the latest versions per the suggestion in #81619 (comment). I am using the current latest versions from https://github.com/dotnet/versions, instead of floating versions, to match what we do elsewhere. I am not sure that we would want to use floating versions, especially in our servicing branch.
|
|
So I merged this fix a couple of hours ago: #81545 It changes the non-existent win10 arm64 helix queue for win11 arm64. I noticed this PR was affected by those non-existent Edit: Here's the PR that missed the others: #81808 cc @hoyosjs |
|
Merged the arm64 Windows queue updates. Closing and reopening this PR. |
|
Using the floating version seems fine -- I think we're going to be pushed onto that eventually anyway. I would prefer if we had fixed versions and then a system for updating them manually, but that doesn't sound like something that's being invested in. |
|
Thanks, I'll leave the fixed versions for now so that we can get this fixed soon, but next time I touch these queues I'll use floating versions. |
Per the suggestions here: #81712 (comment)
…ions instead (#83100) * Fix superpmi_collect-setup.py helix images to use floating instead Per the suggestions here: #81712 (comment) * Update comment at the top --------- Co-authored-by: carlossanlop <carlossanlop@users.noreply.github.com>
ghost
locked as resolved and limited conversation to collaborators
Updating to the latest versions per the suggestion in #81619 (comment). I am using the current latest versions from https://github.com/dotnet/versions, instead of floating versions, to match what we do elsewhere. I am not sure that we would want to use floating versions, especially in our servicing branch.