-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Attempting to JIT compile in Full AOT mode ExecutionEngineException failing tests in CI #73041
Comments
Tagging subscribers to this area: @cston Issue DetailsRunfo Creating Tracking Issue (data being generated)
|
Tagging subscribers to 'os-tvos': @steveisok, @akoeplinger Issue DetailsThese "Attempting to JIT compile" errors are showing up in 100s of different tests. See the failures in https://runfo.azurewebsites.net/view/build/?number=1910126
Runfo Tracking Issue: Attempting to JIT compile in AOT only mode
Build Result Summary
|
The vast majority of tests are failing because it's trying to JIT and that is not supported on devices.
#73061 was merged, which skips the tests on tvOS. Blocking-clean-ci is no longer needed. |
These "Attempting to JIT compile" errors are showing up in 100s of different tests. See the failures in https://runfo.azurewebsites.net/view/build/?number=1910126. These errors are so numerous that it overwhelms UI pages designed to show error lists and will likely interfere with detecting any other CI problems while this remains active.
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-main-3cff2cfeb42c4b83ac/Microsoft.CSharp.Tests/1/testResults.xml?%3Fhelixlogtype%3Dresult
Runfo Tracking Issue: Attempting to JIT compile in AOT only mode
Build Result Summary
The text was updated successfully, but these errors were encountered: