-
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
[wasm][tests][aot] Tests failing due to stacktrace not supported #50957
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
I don't see how it would be possible to implement this, unless we would be manually linking frames with each call, which sounds like a bad idea. |
yeah I think we should probably just skip these with platform detection on AOT |
Only the failing tests, or the entire library? |
Don't skip the library. Leave them active issue for now. We may want to consider an AOT analyzer for cases like this too. Thoughts @marek-safar |
System.Diagnostics.StackTrace
System.Diagnostics.StackTrace
Merging #51676 with this.
|
Having stack traces on wasm is a bit complicated and I think we should revisit this for .net 7. @lewing Any thoughts on moving the milestone ? |
Moving to 7.0.0 |
we're getting enough diagnostic info from the current stacks that this isn't urgent, we'll go over it again when planning for 8 |
Tests failing due to stacktrace APIs not being supported. The relevant tests are disabled.
System.Diagnostics.Tests
System.Runtime.Extensions.Tests
System.IO.Pipelines.Tests
([wasm][tests][aot] System.IO.Pipelines.Tests - failing tests #50959)--
System.Diagnostics.Tests
Logs
The text was updated successfully, but these errors were encountered: