-
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
[browser] mono runtime already exited with 0 #89425
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsError BlobBuild: https://dev.azure.com/dnceng-public/public/_build/results?buildId=350621&view=results {
"ErrorMessage": "mono runtime already exited with",
"BuildRetry": false,
"ExcludeConsoleLog": false
} Reproduction Stepswasm
|
Finally we have also stack trace, WasmTestOnNodeJS-System.Net.Http.Functional.Tests Log
|
We have another Log
|
Another Log
|
Another Log
|
can we close this? |
Hopefully this was fixed by #93472 |
Error Blob
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=350621&view=results
Log: https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-89387-merge-7052a2aebdb04a27be/WasmTestOnNodeJS-System.Net.WebSockets.Client.Tests/1/console.ec43186b.log?helixlogtype=result
Reproduction Steps
wasm
System.Net.WebSockets.Client.Tests
nodeJSKnown issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=350621
Error message validated:
mono runtime already exited with
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/25/2023 9:31:59 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: