Some Windows tests are never finishing

[MarcosJLR]

I have noticed that since PR #2196 was merged into master, the AppVeyor build and the github action main / dhall on windows-latest (push) are both being cancelled for taking too long (60 min on AppVeyor and 360 min on GitHub).

I don't know why it is happening and I think is worth that someone with more experience reviews it 😅

[Gabriella439]

So I just disabled the Appveyor build in factor of the GitHub build, but I'll still need to debug the GitHub build

[sjakobi]

For reference, here's one of the failed Windows jobs: https://github.com/dhall-lang/dhall-haskell/runs/2979018865

[sjakobi]

For comparison, here's the successful CI job from the parent of the problematic c23e4d5: https://github.com/dhall-lang/dhall-haskell/runs/2917448856

(CC @mmhat)

[sjakobi]

Since it seems that the dhall:doctest suite passes all the tests but then fails to finish, I've reported the issue at sol/doctest#300.

[sjakobi]

So the status quo on this issue is that the dhall:doctest test suite is disabled on Windows:

dhall-haskell/dhall/dhall.cabal

Lines 706 to 720 in dc31e3c

	Test-Suite doctest
	Type: exitcode-stdio-1.0
	Hs-Source-Dirs: doctest
	Main-Is: Main.hs
	GHC-Options: -Wall
	Build-Depends:
	base ,
	directory ,
	filepath < 1.5 ,
	mockery < 0.4 ,
	doctest >= 0.7.0 && < 0.19
	if os(windows)
	-- https://github.com/dhall-lang/dhall-haskell/issues/2237
	Buildable: False
	Default-Language: Haskell2010

AFAIK this test suite isn't very important for checking cross-platform correctness, so it's not a big problem. When sol/doctest#300 is fixed or once we're using a more recent GHC version in the Windows builds, we can try re-enabling the test suite.