[wasm] windows/WasmTestOnBrowser tracking issue

[radekdoulik]

These tests currently timeouts on windows

$(MSBuildThisFileDirectory)Microsoft.VisualBasic.Core\tests\Microsoft.VisualBasic.Core.Tests.csproj
$(MSBuildThisFileDirectory)System.IO\tests\System.IO.Tests.csproj
$(MSBuildThisFileDirectory)System.Linq.Expressions\tests\System.Linq.Expressions.Tests.csproj
$(MSBuildThisFileDirectory)System.Memory\tests\System.Memory.Tests.csproj
$(MSBuildThisFileDirectory)System.Runtime\tests\System.Runtime.Tests.csproj
$(MSBuildThisFileDirectory)System.Private.Xml\tests\Writers\XmlWriterApi\System.Xml.RW.XmlWriterApi.Tests.csproj
$(MonoProjectRoot)sample\wasm\browser\Wasm.Browser.Sample.csproj
$(RepoRoot)\src\tests\BuildWasmApps\Wasm.Build.Tests\Wasm.Build.Tests.csproj

Some of these might be caused by emscripten cache locking problem.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

These tests currently timeouts on windows

$(MSBuildThisFileDirectory)Microsoft.VisualBasic.Core\tests\Microsoft.VisualBasic.Core.Tests.csproj
$(MSBuildThisFileDirectory)System.IO\tests\System.IO.Tests.csproj
$(MSBuildThisFileDirectory)System.Linq.Expressions\tests\System.Linq.Expressions.Tests.csproj
$(MSBuildThisFileDirectory)System.Memory\tests\System.Memory.Tests.csproj
$(MSBuildThisFileDirectory)System.Runtime\tests\System.Runtime.Tests.csproj
$(MSBuildThisFileDirectory)System.Private.Xml\tests\Writers\XmlWriterApi\System.Xml.RW.XmlWriterApi.Tests.csproj
$(MonoProjectRoot)sample\wasm\browser\Wasm.Browser.Sample.csproj
$(RepoRoot)\src\tests\BuildWasmApps\Wasm.Build.Tests\Wasm.Build.Tests.csproj

Some of these might be caused by emscripten cache locking problem.

Author:	radekdoulik
Assignees:	radekdoulik
Labels:	arch-wasm, area-Build-mono
Milestone:	-

[radical]

We should check if these can be enabled now, maybe after the 3.1.1 bump .

[radical]

@ilonatommy we could try to enable these to see if they are passing now.

[ilonatommy]

The situation changed a bit. Running dotnet build /t:Test src/libraries/TESTED_DIR p:TargetOS=Browser /p:Configuration=Release /p:BrowserHost=Windows /p:Scenario=WasmTestOnBrowser results in:

• Microsoft.VisualBasic.Core [FAIL] CurrentDirectorySet and CurrentDirectoryGet, [wasm] Microsoft.VisualBasic.Core tests for CurrentDirectory fail for Browser on Windows #70887.
• System.IO [PASS]
• System.Linq.Expressions [PASS]
• System.Memory [PASS]
• System.Runtime [PASS]
• System.Xml.RW.XmlWriterApi [PASS]
• Wasm.Build.Tests [PASS]

Wasm.Browser.Sample does not exist anymore.

I'm adding a PR that will enable test suites and will block only these few failing ones.