-
Couldn't load subscription status.
- Fork 5.2k
[browser][MT] fix CaptureContextFromParameter and SealJSImportCapturing #96504
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] fix CaptureContextFromParameter and SealJSImportCapturing #96504
Conversation
- new test JSObject_CapturesAffinity - fixed ExecutorType.NewThread in tests - cleanup
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
...ropServices.JavaScript/src/System/Runtime/InteropServices/JavaScript/JSHostImplementation.cs
Show resolved
Hide resolved
...Runtime.InteropServices.JavaScript/src/System/Runtime/InteropServices/JavaScript/JSObject.cs
Outdated
Show resolved
Hide resolved
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
...time.InteropServices.JavaScript/src/System/Runtime/InteropServices/JavaScript/JSWebWorker.cs
Show resolved
Hide resolved
...rvices.JavaScript.UnitTests/System/Runtime/InteropServices/JavaScript/WebWorkerTestHelper.cs
Outdated
Show resolved
Hide resolved
|
looks good so far |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
… least one available threads is loaded into emscripten pool
|
/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). |
|
All CI failures are known |
CaptureContextFromParameterandSealJSImportCapturingJSObject_CapturesAffinityExecutorType.NewThreadin testsschedule_background_execandmono_wasm_invoke_import_async