Larry Ewing

``` :\helix\work\correlation\build\wasm-shared\WasmApp.Common.targets(832,5): error : Failed to compile C:\helix\work\workitem\e\wasm_build\obj\wasm\for-build\System.Private.CoreLib.dll.bc -> C:\helix\work\workitem\e\wasm_build\obj\wasm\for-build\System.Private.CoreLib.dll.o [C:\helix\work\workitem\e\publish\ProxyProjectForAOTOnHelix.proj] C:\helix\work\correlation\build\wasm-shared\WasmApp.Common.targets(832,5): error : C:\helix\work\workitem\e\publish>C:\Windows\System32\chcp.com 65001 1>nul [C:\helix\work\workitem\e\publish\ProxyProjectForAOTOnHelix.proj] C:\helix\work\correlation\build\wasm-shared\WasmApp.Common.targets(832,5): error : C:\helix\work\workitem\e\publish>setlocal [C:\helix\work\workitem\e\publish\ProxyProjectForAOTOnHelix.proj] C:\helix\work\correlation\build\wasm-shared\WasmApp.Common.targets(832,5): error : C:\helix\work\workitem\e\publish>set errorlevel=dummy [C:\helix\work\workitem\e\publish\ProxyProjectForAOTOnHelix.proj] C:\helix\work\correlation\build\wasm-shared\WasmApp.Common.targets(832,5):...

see also https://github.com/dotnet/runtime/issues/99150

Instead of worrying about what caused it to start failing recently the bundled clang is definitely still 32bit (as @SingleAccretion pointed out) and that seems to be underlying cause so...

opened https://github.com/dotnet/runtime/pull/101827 to disable the failing bits in the meantime

reopening to reenable the disabled tests and verify the fix |24-Hour Hit Count|7-Day Hit Count|1-Month Count| |---|---|---| |33|248|358|

This will not get serviced, we can keep it around for now to keep analysis clean for net7.0 servicing.

also https://github.com/dotnet/runtime/issues/59678

and https://github.com/dotnet/runtime/issues/101016

> @lewing anything else needed on this? I'm fixing a couple of the issues on our side then I will update it again.

Actually there is no harm in taking as is. I'll do a follow-up if this lands ahead of the other work.