-
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
how can I run runtime tests with monovm on ios? #85160
Comments
Tagging subscribers to this area: @directhex Issue Detailsnull
|
/cc @SamMonoRT |
Tagging subscribers to 'os-ios': @steveisok, @akoeplinger Issue Detailsnull
|
@srxqds - please follow instructions in https://github.com/dotnet/runtime/blob/main/docs/workflow/README.md and let us know if you have any questions. |
The instruction what I follow is https://github.com/dotnet/runtime/blob/main/docs/workflow/testing/mono/testing.md I try to build the runtime tests for iOSSimulation use command in src/tests ./build.sh -mono os iOSSimulation arm64 release It will pass but the test will crash while running build the runtime tests for iOS device use command ./build.sh -mono os iOS arm64 release It will throw many exceptions: Need list of AOT files for device builds. |
Check out the following instructions https://github.com/dotnet/runtime/blob/main/docs/workflow/testing/libraries/testing-apple.md. They are for the library tests, but could be useful.
First, run the following command from the root directory to build the runtime:
Second, run the following command from
Please note that a subset of runtime tests is supported currently. We will introduce more tests in the future.
Such error is usually happening when AOT compilation was disabled and |
./build.sh -mono os iOS arm64 release /p:DevTeamProvisioning=ZF3Z3HS5W2 /p:ForceAOT=True /p:LibrariesConfiguration=Release The problam still exists |
Can you share the error logs? Parameter |
There is a error: xcrun simctl install 15ED0483-DDCB-4C06-B4E8-5230AB119F52 ./artifacts/tests/coreclr/iOSSimulator.arm64.Release/JIT/Math/JIT_Math.app the following output is the code I add in AppleAppBuilder.cs execute function |
Thank you. According to the logs, there are artifacts built for The steps should be: rm -rf ./artifacts
./build.sh -arch arm64 -os ios -s mono+libs -c Release
./src/tests/build.sh os ios arm64 Release -mono tree tracing/eventpipe /p:LibrariesConfiguration=Release Also, I would recommend trying HelloiOS sample app to get familiar with the process, and to verify if the runtime is built correctly. To run the HelloiOS sample app, configure parameters in the Makefile and run |
So follow your instructions : then still the same error: ===========Apple builder build:==bindir:================/Users/game-netease/dotnet/runtime/artifacts/tests/coreclr/obj/iOS.arm64.Release/Managed/./build/iOSApps/tracing_eventpipe/bin-tracing_eventpipe-arm64 False ================== |
The provided command appears to have an invalid |
./build.sh os iOS arm64 Release -mono tree tracing/eventpipe /p:DevTeamProvisioning=ZF3Z3HS5W2 /p:LibrariesConfiguration=Release The command is invalid,the errors below: The switch that responds to file appends: |
Could you check if you are using the latest version from the main branch? If you are using the latest version and the issues still persists, I suggest you zip and share your local version of the runtime repository here, so I can try to reproduce the issue locally. Thank you. |
The branch what I used is release/7.0 instead of main, is that OK? |
The iOS runtime tests have been introduced recently, in #79169. Please try with the main branch. |
Ok, I will check out main branch and try it, thank you anyway,why we must focus on tracing/eventpipe? what about the other tests? Like JIT/Math, GC... and so on? |
We plan to include other testing groups that could be executed on iOS/iOSSimulator in the future. It may be possible to filter other testing groups for execution, but they have not been tested yet. If you find that certain groups can be run on a device without any modifications, we encourage you to contribute by opening a PR, or providing details here. |
Ok, thank you for help! |
Thanks! I will close this issue, but feel free to reopen it if you have further questions. |
No description provided.
The text was updated successfully, but these errors were encountered: