-
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] DebuggerTests.MiscTests.DebuggerTests.MiscTests.TestDebugUsingMultiThreadedRuntime
failing
#89909
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=361663 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "",
"ErrorPattern": "at Newtonsoft.Json.Linq.JArray.get_Item",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
|
|
Here the debugger test is calling into runtime via legacy JS interop method (probably on main thread) but it's not having correct GC transition barrier. @kg @lambdageek is my analysis right ? In which case that should be separate issue.
...snip
|
Yea I think you're right @pavelsavara |
I will work on it today. |
So, legacy interop is gone now and with it the assumed GC boundary problems of it.
It look like deadlock. |
removing blocking-clean-ci as it has not failed in 30 days
|
leaving open since these may still be running in servicing but these tests are disabled in main |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=361663
Build error leg or test failing: DebuggerTests.MiscTests.DebuggerTests.MiscTests.TestDebugUsingMultiThreadedRuntime
Pull request: #89890
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎⚠️ Provided build not found. Provide a valid build in the "Build: 🔎" line.
Result validation:
Validation performed at: 8/23/2023 4:28:55 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: