Jan Kotas

The bulk of this port was done already. There are a few discrepancies to resolve in corner cases described in https://github.com/dotnet/runtime/issues/32708.

> Switch from using bin to artifacts This will be a major breaking change and generate work for every other project out there. We should think twice whether this cosmetic...

> @jkotas Are you referring to any change we make to the output path format, or specifically this version of the proposal which would switch to using an artifacts path?...

> GCSampledObjectAllocation > masks referencing allocation (COR_PRF_MONITOR_OBJECT_ALLOCATED, COR_PRF_ENABLE_OBJECT_ALLOCATED) should apply to all heaps. How is this expected to work for file-backed non-GC heap segments? I think it would be more...

> I was assuming that when the time came to support that scenario (which didn't appear to be now) We do not have general support for it. We support it...

> We have libc documented here. Would it make sense to document libstdc++, too? > @sbomer @jkotas I think documenting libc version is good enough. Versions of other libraries are...

If you would like to promote the current runtimelab project to "shipping with dotnet/runtime", the proper way to do that is by integrating it to dotnet/runtime.

It is fine to make small target changes in dotnet/runtime repo to support the projects that we run in runtimelab. dotnet/runtime repo should not be taking dependencies on runtimelab artifacts...

It is failing on #101767 with the fix.

> Wow, even with tiered jit disabled and finalizer thread blocked, the CI is still flaky. My guess is that the next problem are the event source background threads.