Uh oh!
There was an error while loading. Please reload this page.
[tests] Stand up iOS arm runtime tests and enable tracing/eventpipe tests - #79169
Conversation
ghost
commented
Dec 2, 2022
Tagging subscribers to this area: @directhex Issue DetailsFixes #74891 On iOS, runtime tests were previously only stood up on x64 (Simulator) in #43954.
|
There was a problem hiding this comment.
I'm a little confused here; what happens if we are running iOSSimulator and both RunAOTCompilation and MonoForceInterpreter are true? Does this change how iOSSimulator tests are run?
There was a problem hiding this comment.
For iOSlike devices and arm based simulators, AOT is needed for the tests to build. (At least that was the case for library tests, which motivated this PR #76551) When setting RunAOTCompilation and MonoForceInterpreter to true, what will happen is AOT will be ran, and if anything goes wrong, interp will be the fallback instead of JIT (which is important because JIT does not work on iOSlike platforms).
I believe the RunAOTCompilation is necessary here for arm architectures, but we can exclude x64 if thats preferred.
mdh1418
commented
Dec 16, 2022
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 2 pipeline(s). |
mdh1418
commented
Dec 19, 2022
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 2 pipeline(s). |
mdh1418
commented
Dec 19, 2022
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Uh oh!
There was an error while loading. Please reload this page.
naricc
commented
Dec 19, 2022
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 2 pipeline(s). |
naricc
commented
Dec 20, 2022
/azp run runtime-ioslike |
|
Azure Pipelines successfully started running 1 pipeline(s). |
naricc
commented
Jan 6, 2023
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines failed to run 2 pipeline(s). |
kotlarmilos
commented
Apr 13, 2023
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 2 pipeline(s). |
kotlarmilos
commented
Apr 13, 2023
The failure shouldn't be related. It has been tracked in dotnet/arcade#11683. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
kotlarmilos
commented
Apr 14, 2023
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 2 pipeline(s). |
kotlarmilos
commented
Apr 17, 2023
/azp run runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mdh1418
commented
Apr 17, 2023
/azp run runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kotlarmilos
commented
Apr 18, 2023
/azp run runtime-ioslike,runtime-ioslikesimulator |
|
Azure Pipelines successfully started running 2 pipeline(s). |
kotlarmilos
commented
Apr 18, 2023
Failures shouldn't be related. The TCP failure is known issue dotnet/arcade#11683. |
Uh oh!
There was an error while loading. Please reload this page.
Fixes#74891
On iOS, runtime tests were previously only stood up on x64 (Simulator) in #43954.
This PR looks to extend the runtime testing coverage to iOS devices and arm simulators by doing the following:
Fixes: #81233