Skip to content

Conversation

@akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Jun 14, 2022

With dotnet/runtime#62501 we were only waiting for completion of the DelegatingExecutionSummarySink, not the DelegatingXmlCreationSink.

Since DelegatingXmlCreationSink doesn't provide a callback when testing is done we need to add a wrapper execution sink that listens for the ITestAssemblyFinished message.

I also noticed we were using MemoryStream.ToArray() when sending the results which creates an additional copy that we can avoid.

Fixes #903

With dotnet/runtime#62501 we were only waiting for
completion of the DelegatingExecutionSummarySink, not the DelegatingXmlCreationSink.

Since DelegatingXmlCreationSink doesn't provide a callback when testing is done we
need to add a wrapper execution sink that listens for the ITestAssemblyFinished message.

Fixes dotnet#903
@akoeplinger akoeplinger merged commit 5a55841 into dotnet:main Jun 14, 2022
@akoeplinger akoeplinger deleted the fix-wasm branch June 14, 2022 13:37
akoeplinger added a commit to akoeplinger/xharness that referenced this pull request Jul 25, 2022
akoeplinger added a commit to akoeplinger/xharness that referenced this pull request Jul 25, 2022
akoeplinger added a commit to akoeplinger/xharness that referenced this pull request Jul 25, 2022
akoeplinger added a commit that referenced this pull request Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[wasm] testResults.xml can end up with zero results if some particular tests are part of the run

2 participants