-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[mono]Re-enable runtime tests on Android arm64 #49662
[mono]Re-enable runtime tests on Android arm64 #49662
Conversation
Tagging subscribers to this area: @directhex Issue Details
|
Draft Pull Request was automatically closed for inactivity. It can be manually reopened in the next 30 days if the work resumes. |
b545a82
to
1ecc87b
Compare
e450b71
to
773316c
Compare
5bad1fe
to
e8a4ecd
Compare
Waiting for dotnet/xharness#610 for further investigation of the timeout issue. |
19fdcc0
to
1ea6594
Compare
This issue was not related to this PR any more. |
c56d203
to
9b65d58
Compare
Failure of workitem PayloadGroup0 was due to a known issue #11063
|
0b0151c
to
112546e
Compare
@akoeplinger - what needs to be done to enable these only on rolling builds as we had discussed a few weeks back ? @fanyang-mono - LGTM - I'll approve, but please confirm with @akoeplinger prior to merging. |
The failures on windows arm64 were irrelevant to this PR. There are two tracking issues for it dotnet/core-eng#13324 and dotnet/core-eng#13292 |
702272c
to
160850a
Compare
I am merging this now. @akoeplinger if there is anything needs to be changed after reviewing, please leave a comment. |
Fixes #45568 Fixes #47850
Before this PR, there were only 475 runtime tests running on Android arm64 and it took more than 3 hours to run those tests. With this PR, there are 2,429 runtime tests running on Android arm64 now and it takes around 1 hour to run them.
Tests to only run on rolling build, since there aren't enough Android devices.