Nathan Ricci

@adamsitnik So I am planning to start work on this soon, and am thinking about the design now. I've never done anything with source generators before and want to make...

This is still happening in dotnet/runtime, should I create a new issue there? @SamMonoRT

@SamMonoRT It looks like we are still off by similar amounts, compared to coreclr, in dotnet runtime: mono: https://pvscmdupload.blob.core.windows.net/reports/allTestHistory%2frefs%2fheads%2fmain_x64_ubuntu%2018.04_LLVM%3dfalse_MonoAOT%3dfalse_MonoInterpreter%3dfalse_RunKind%3dmicro_mono%2fMicroBenchmarks.Serializers.Xml_FromStream(ClassImplementingIXmlSerialiable).XmlSerializer_.html coreclr: https://pvscmdupload.blob.core.windows.net/reports/allTestHistory%2frefs%2fheads%2fmain_x64_ubuntu%2018.04%2fMicroBenchmarks.Serializers.Xml_FromStream(ClassImplementingIXmlSerialiable).XmlSerializer_.html

So, `mono_determine_physical_ram_available_size` is in memfuncs.c is used for is to calculate the GCMemoryInfo.MemoryLoadBytes field. My understanding from when I implemented the GC.GetMemoryInfo functions was that MemoryLoadBytes was supposed to be...

@rokonec I can also help walkthrough how the wasm runtime tests are built. I think some of these errors may have been fixed by https://github.com/dotnet/runtime/pull/75939. Honestly reading through the issue...

@rokonec A rough description of the wasm runtime tests. Each test is an individual project. When the tests are built, a xunit wrapper and bash wrapper are generated. When run,...

I will disable the test for now.

@radical Do we need to rework how the wasm toolchain works? Or do we already support running it against whatever is in the the workload?