Runtime_72845 timing out in gcstress

[jakobbotsch]

https://dev.azure.com/dnceng/public/_build/results?buildId=1935562&view=ms.vss-test-web.build-test-results-tab

This is a recently added test so not a regression. The test is comparing two large lists, so likely to be gcstress incompatible, but we should probably verify that there is no deadlock.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Issue Details

---

https://dev.azure.com/dnceng/public/_build/results?buildId=1935562&view=ms.vss-test-web.build-test-results-tab

This is a recently added test so not a regression. The test is comparing two large lists, so likely to be gcstress incompatible, but we should probably verify that there is no deadlock.

Author:	jakobbotsch
Assignees:	-
Labels:	area-CodeGen-coreclr, untriaged
Milestone:	-

[jakobbotsch]

@JulieLeeMSFT can you assign this? GCStress is still failing due to this one.

[jakobbotsch]

Actually I'll just look at this, I have some cycles available.

[jakobbotsch]

This test takes a long time to run on x64 too, so I think it is just GC stress incompatible and nothing inherent about arm64 here.

[JulieLeeMSFT]

Thanks @jakobbotsch.