Uh oh!
There was an error while loading. Please reload this page.
[wasm] Fix scenario specific tests - #64800
Conversation
Co-authored-by: Ankit Jain <radical@gmail.com>
ghost
commented
Feb 4, 2022
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
maraf
commented
Feb 4, 2022
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Feb 4, 2022
|
premun
commented
Feb 4, 2022
FWIW this setting is now true by default (dotnet/arcade#8216): <EnableXHarnessTelemetry>true</EnableXHarnessTelemetry>And as such can be omitted. |
maraf
commented
Feb 4, 2022
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
radical
commented
Feb 4, 2022
Add |
maraf
commented
Feb 4, 2022
I'm trying to fix wasm on browser here. It seems that the path where |
radical
commented
Feb 4, 2022
I merged my PR to enable library tests on nodejs, fyi. |
maraf
commented
Feb 4, 2022
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
browserornodejsandnodejsonlyfolders.System.Net.WebSockets.Client.Testson NodeJS, before we fix NodeJS [wasm] Fix WebSocket tests on NodeJS #64330