-
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][debugger] Trying to fix MT debugging experience. #90771
Conversation
Tagging subscribers to this area: @thaystg Issue Detailsnull
|
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
First try passed the MT debugger tests. |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsI'm doing this workaround to avoid memory allocation while debugging a MT wasm app, it looks like there is some failure while updating the memory in all the workers while some of them are paused.
|
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm-dbgtests |
Azure Pipelines successfully started running 1 pipeline(s). |
I'm doing this workaround to avoid memory allocation while debugging a MT wasm app, it looks like there is some failure while updating the memory in all the workers while some of them are paused.
This will fix the CI and also improve the customer experience.