[wasm] workaround test results corruption#61841
Conversation
|
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Details
In hope that it fixes or surfaces more the issue #61749
|
|
Tagging subscribers to 'arch-wasm': @lewing Issue Details
In hope that it fixes or surfaces more the issue #61749
|
lewing
left a comment
There was a problem hiding this comment.
Looks good once the test changes are reverted
|
|
|
Work in progress here dotnet/xharness#771 |
This reverts commit 5102ad2.
|
Will need new nuget binaries from dotnet/xharness#771 |
|
/azp run runtime-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@radical @maraf @lewing I think this fixes XML corruption problem for WASM. @premun I know that you are working on bumping all other dependencies too in #61668 shall we wait for that instead of merging it here ? |
|
Please merge it here |
|
You can ignore the Wasm/Windows/AOT tests. |
|
You can ignore the Wasm/Windows/WBT tests also. I am disabling them in #61937 . |
WASM EXIT. This is bit pointless because it goes into the same WS buffer, on the other hand, we know that we reached that point before the browser process was stopped.Fixes #61749