-
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] Fix scenario specific tests #64800
Conversation
Co-authored-by: Ankit Jain <radical@gmail.com>
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
|
FWIW this setting is now true by default (dotnet/arcade#8216): <EnableXHarnessTelemetry>true</EnableXHarnessTelemetry> And as such can be omitted. |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
Add |
I'm trying to fix wasm on browser here. It seems that the path where |
I merged my PR to enable library tests on nodejs, fyi. |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
browserornodejs
andnodejsonly
folders.System.Net.WebSockets.Client.Tests
on NodeJS, before we fix NodeJS [wasm] Fix WebSocket tests on NodeJS #64330