-
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][MT] more testing and cleanup #94466
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Detailsnull
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
@@ -5,10 +5,11 @@ | |||
<TestRuntime>true</TestRuntime> | |||
<EnableDefaultItems>true</EnableDefaultItems> | |||
<IncludeRemoteExecutor>true</IncludeRemoteExecutor> | |||
<_WasmPThreadPoolSize Condition="'$(MonoWasmBuildVariant)' == 'multithread'">100</_WasmPThreadPoolSize> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😱
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the test is allocating lot of threads. I suspect that we are still not freeing them fast enough.
If we adopt deputy design, we could have dynamic thread allocation.
It's obvious this is not sustainable. On the other hand, this is just a test, not production code.
Please add comments for each explicit threadpool size:
|
There are know failures #89409 |
mono_coop_sem_post
for MT GCOther
mono_threads_wasm_is_browser_thread
tomono_threads_wasm_is_ui_thread
mono_threads_wasm_browser_thread_tid
tomono_threads_wasm_ui_thread_tid
mono_threads_wasm_async_run_in_target_thread_vii
diagnostics_cwraps
tothreading_cwraps
Fixes #72101
Fixes #91593