.NET Framework test runs are _super_ slow in CI

[brianrourkeboll]

(Put this under https://github.com/dotnet/fsharp/labels/Contributor%20Pain, I guess.)

When did the Windows desktop (.NET Framework) build+test runs start taking ~3× as long as the other build+test runs? Was this an expected outcome of some recent change?

The Linux, MacOS, WindowsNoRealsig_testCoreclr, etc., runs take about half an hour now, while the WindowsNoRealsig_testDesktop and WindowsCompressedMetadata desktop_release runs now take more than an hour and a half.

I feel like they didn't take that long even just a couple months ago, either absolutely or relatively. I remember them taking maybe 55 minutes or something (although Azure Pipelines runs older than 30 days have been purged, so I guess I can't prove it).

[vzarytovskii]

There are more of them on desktop. Fsharpqa and Cambridge suites are framework only (not 100% sure about the latter though).

I also won't be surprised if we run VS tests as part of desktop framework, which are very (VERY) slow.

I wanna say it's kinda expected, but nothing we can't fix one way or another

[brianrourkeboll]

There are more of them I guess. Fsharpqa and Cambridge suites are framework only

Yeah, I do remember the desktop runs always taking longer, but I remember them taking ~55 minutes until recently, whereas they now take ~90 minutes.