-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[wasm][aot] test fails because it calls Type.GetType ("FOO")
which uses a stack walk to obtain the calling assembly which is used to resolved FOO
#52393
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsSeen in https://github.com/dotnet/runtime/pull/52004/checks?check_run_id=2517540700
|
The earlier one (dotnet#51960) was fixed. New: dotnet#52393
* [wasm][aot] System.Runtime.Tests failing with a different issue now The earlier one (#51960) was fixed. New: #52393 * Enable Common.Tests test tracked in #50955, already fixed on main * [wasm] System.Reflection.Tests - update to track change from crash to a .. test failure. Issue: #51673 * Re-enable System.Collections.Tests, issue: #51037 * Disable Microsoft.Extensions.Logging.Generators, and System.IO.Pipelines Issue: #52384 Issue: #50959 * Enable two System.Reflection.Metadata* tests Issue: #51958 * Fix path for Microsoft.Extensions.Logging.Generators.Tests
Sometimes it fails in the WaitHandle tests, a small testcase:
This runs with the interpreter, and hangs with AOT. |
RuntimeError: invalid index into function table
Instead of a crash, or build error, we get test failures (last week or so):
|
Most of these are AOT stack trace related |
The stacktrace related tests have been disabled. Last remaining test:
|
this doesn't fail with eat? |
Yep <test name="System.Tests.TypeTests.GetTypeByName_InvokeViaReflection_Success"
type="System.Tests.TypeTests"
method="GetTypeByName_InvokeViaReflection_Success"
time="0.000297"
result="Pass" /> |
This is not going to work with aot because it calls Type.GetType ("FOO"); which uses a stack walk to obtain the calling assembly which is used to resolved FOO. |
Should the test be disabled with this as the ActiveIssue, or just disable it? |
Just disable it imho it's not going to get fixed. |
Type.GetType ("FOO")
which uses a stack walk to obtain the calling assembly which is used to resolved FOO
System.Runtime.Tests
Seen in https://github.com/dotnet/runtime/pull/52004/checks?check_run_id=2517540700
The text was updated successfully, but these errors were encountered: