Larry Ewing

cc @vitek-karas

saw it again on https://github.com/dotnet/runtime/pull/73939 https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-73939-merge-646ef37e77d843aaa0/chrome-DebuggerTests/1/console.3ea30947.log?helixlogtype=result

``` [xUnit.net 00:36:58.27] DebuggerTests.ExceptionTests.ExceptionTestUncaughtWithReload [FAIL] Failed DebuggerTests.ExceptionTests.ExceptionTestUncaughtWithReload [1 s] Error Message: [pause1] Expected: DebuggerTests.ExceptionTestsClass.TestUncaughtException.run Actual: invoke_static_method Stack Trace: at DebuggerTests.DebuggerTestBase.AssertEqual(Object expected, Object actual, String label) in /_/src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestBase.cs:line 1184 at DebuggerTests.ExceptionTests.ExceptionTestUncaughtWithReload()...

> Regarding C# / .NET, as far as I understood, our current implementation doesn't make use of the wasm GC proposal because its capabilities were not enough. @lewing would know...

given that is works on earlier 6.0.xxx sdks I'm not sure what is going on but https://github.com/dotnet/runtime/pull/72147 is worth landing for many reasons

@javiercn can you have a look at the static web assets tests @jeffschwMSFT there are several Microsoft.NET.Build.Tests failures that are not wasm related.

It looks like a crossgen check is running when targeting blazor-wasm and understandably fails to find a suitable runtime, could https://github.com/dotnet/sdk/pull/27159 have anything to do with it?

cc @rainersigwald

see also https://github.com/dotnet/runtime/discussions/76091

~This seems to have come in with the new sdk~