Uh oh!
There was an error while loading. Please reload this page.
[wasm] workaround test results corruption - #61841
Conversation
ghost
commented
Nov 19, 2021
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Details
In hope that it fixes or surfaces more the issue #61749
|
ghost
commented
Nov 19, 2021
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
Uh oh!
There was an error while loading. Please reload this page.
pavelsavara
commented
Nov 19, 2021
|
pavelsavara
commented
Nov 19, 2021
Work in progress here dotnet/xharness#771 |
This reverts commit 5102ad2.
pavelsavara
commented
Nov 20, 2021
Will need new nuget binaries from dotnet/xharness#771 |
pavelsavara
commented
Nov 22, 2021
/azp run runtime-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 22, 2021
/azp run runtime-manual |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Nov 22, 2021
@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 ? |
premun
commented
Nov 22, 2021
Please merge it here |
radical
commented
Nov 22, 2021
You can ignore the Wasm/Windows/AOT tests. |
Uh oh!
There was an error while loading. Please reload this page.
radical
commented
Nov 22, 2021
You can ignore the Wasm/Windows/WBT tests also. I am disabling them in #61937 . |
Uh oh!
There was an error while loading. Please reload this page.
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