-
Notifications
You must be signed in to change notification settings - Fork 5k
[wasm][aot][windows] Crash in Microsoft.Extensions.Logging.Tests
#64725
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
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue Details
Crash:
|
radical
added a commit
to radical/runtime
that referenced
this issue
Feb 3, 2022
`Microsoft.Extensions.HostFactoryResolver.Tests`: dotnet#64724 `Microsoft.Extensions.Logging.Tests`: dotnet#64725
Looks like same issue in emscripten as mentioned in #64724 (comment) |
radical
added a commit
that referenced
this issue
Feb 4, 2022
* [wasm][aot] Disable failing tests `Microsoft.Extensions.HostFactoryResolver.Tests`: #64724 `Microsoft.Extensions.Logging.Tests`: #64725 * [wasm][aot] Disable `System.Text.Json.SourceGeneration.Roslyn3.11.Unit.Tests` .. on linux. Fixes #64762 . Real issue being tracked in #61339 * disable failing nodejs samples * [wasm] Disable more failing tests System.Linq.Tests: #64774 System.Text.Json.Tests: #64775 * Disable System.Text.RegularExpressions.Tests due to issue#64769
radekdoulik
added a commit
to radekdoulik/runtime
that referenced
this issue
Feb 4, 2022
lewing
pushed a commit
that referenced
this issue
Feb 10, 2022
radekdoulik
added a commit
to radekdoulik/runtime
that referenced
this issue
Feb 14, 2022
Fix dotnet#64724 and dotnet#64725 The tests were crashing because calling the memalign function, which was not exported.
lewing
pushed a commit
that referenced
this issue
Feb 14, 2022
13 tasks
This started with the 2.0.34 bump, which has been rolled back now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Hit on #62499
Build, and log.
Crash:
cc @radekdoulik @vargaz
The text was updated successfully, but these errors were encountered: