System.Text.Json.Tests hang on a Checked CoreCLR

[safern]

https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-45451-merge-d5c2411bf7a94e53aa/System.Text.Json.Tests/console.8c3fdb0f.log?sv=2019-07-07&se=2020-12-22T01%3A58%3A57Z&sr=c&sp=rl&sig=jVvW5f1Z0z%2BebQhjuzWnYHsuErZs%2BRgJdJI0dR22FP4%3D

/private/tmp/helix/working/AACC08F8/w/BA4409BB/e /private/tmp/helix/working/AACC08F8/w/BA4409BB/e
  Discovering: System.Text.Json.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Text.Json.Tests (found 2262 of 2294 test cases)
  Starting:    System.Text.Json.Tests (parallel test collections = on, max threads = 4)
   System.Text.Json.Tests: [Long Running Test] 'System.Text.Json.Serialization.Tests.ConstructorTests_String.ReadSimpleObjectAsync', Elapsed: 00:07:21
[Long Running Test] 'System.Text.Json.Tests.Utf8JsonWriterTests.Writing3MBBase64Bytes', Elapsed: 00:07:19
[Long Running Test] 'System.Text.Json.Serialization.Tests.ConstructorTests_Span.MultipleTypes', Elapsed: 00:07:24
[Long Running Test] 'System.Text.Json.Tests.JsonDocumentTests.ParseJson_UnseekableStream_Async_BadBOM', Elapsed: 00:06:39
[Long Running Test] 'System.Text.Json.Tests.Utf8JsonReaderTests.ReadInvalidJsonStringsWithComments', Elapsed: 00:02:03
[Long Running Test] 'System.Text.Json.Serialization.Tests.StreamTests.RoundTripAsync', Elapsed: 00:05:37
[Long Running Test] 'System.Text.Json.Serialization.Tests.NumberHandlingTests.DictionariesRoundTrip', Elapsed: 00:05:04
[Long Running Test] 'System.Text.Json.Serialization.Tests.ConstructorTests_Stream.MultipleTypes', Elapsed: 00:05:22
[Long Running Test] 'System.Text.Json.Serialization.Tests.ContinuationTests.ShouldWorkAtAnyPosition_Sequence', Elapsed: 00:04:02

Happened on OSX on a Checked CoreCLR.

I just checked on Kusto and this has happened 11 times in the past day.

Hit in: #45451

Maybe we just need to mark as SkipOnCoreClr("", RuntimeConfiguration.Checked)?

[safern]

Related: #35927

[layomia]

Clean CI unblocked with #45505.

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of the experimental issue cleanup initiative we are currently trialing in a limited number of areas. Please share any feedback you might have in the linked issue.

[ghost]

This issue will now be closed since it had been marked no recent activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.