Disable android arm64 tests on PRs #49844
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. |
safern
force-pushed
the
DisableAndroidArm64
branch
from
022a777 to
c25ff20
Compare
safern
force-pushed
the
DisableAndroidArm64
branch
from
c25ff20 to
64c9368
Compare
steveisok
approved these changes
Mar 19, 2021
|
I'm ok with merging this now. |
stephentoub
approved these changes
Mar 19, 2021
|
Thanks, @safern and @steveisok. |
|
Doubled checked and the expanded build on this PR is not running tests for Android arm64 so I will merge this to unblock other PRs. |
mdh1418
pushed a commit
to steveisok/runtime
that referenced
this pull request
Mar 23, 2021
This reverts commit f64246c.
ghost
locked as resolved and limited conversation to collaborators
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.
Currently we are waiting for more Android devices to be installed into the helix queue. That is causing the runtime-staging pipeline to timeout very frequently.
Run the tests only on rolling until we get more devices.