[release/6.0] Update arm queues #81858
Merged
Conversation
This file contains 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
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
ghost
assigned 
carlossanlop
approved these changes
Feb 9, 2023
|
If you don't mind, I'll merge the PR as soon as all the ARM* queues finish and don't show failures anymore. |
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Feel free. There were more failures on a 16.04 machine. Fingers crossed that this is the last instance. Also feel free to push to this PR if it's still red and you want to iterate on it. |
carlossanlop
reviewed
Feb 9, 2023
carlossanlop
reviewed
Feb 9, 2023
carlossanlop
reviewed
Feb 9, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Updating arm queues to fix ci failures. I am using floating versions per the discussion in #81712.
Hoping this fixes #81391, since it looks likely to be the same root cause as #81391.