Jan Kotas

I have opened https://github.com/dotnet/runtime/issues/73246 to have this tracked. It is not the first time that this option is being discussed.

> How does that work with VS? Is this a command line only story? VS test does not work for the inner loop if you work on the core runtime,...

> This wouldn't help coreclr tests, right? Also, it wouldn't help libraries tests in case the hang is in the runtime (GC, etc.).

Yes, I think it should be labels. The set of labels to use for this has to be more opinionated. We should only need two labels for what we are...

I think that the merge-on-red labels need to be assigned automatically by the build analysis, so there is no manual work required to maintain them and it is done consistently....

The label allows anybody to use the regular github issue queries, narrow the search by additional conditions, etc. The label can be manually corrected when the automation gets it wrong....

The docs are at https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-2.2 . The minimal sample linked from the docs is not a full blown ASP.NET project, but it still carries some of the baggage with it:...

@corerb `DataGridViewRowCollection.RowArrayList` has its own custom sort implementation: https://github.com/dotnet/winforms/blob/d46ad2e8dc76248739d9ae22b28b399a6a6b299e/src/System.Windows.Forms/src/System/Windows/Forms/DataGridViewRowCollection.RowArrayList.cs#L35 . Unless the implementation is refactored to use the sort implementation from the core libraries, you would not be able to...

Added ErrorMessage signature to get this issue auto-detected by Build analysis

The failures looks like a real problem with the change to me.