Commit 3c339d2e authored by kristenk's avatar kristenk Committed by Mikhail Glushenkov

Use hackage-repo-tool when running cabal-testsuite on AppVeyor (closes #5204).

I disabled one test that still fails on Windows:
PackageTests/NewBuild/CustomSetup/RemotePackageWithCustomSetup/build-package-from-repo-with-custom-setup.test.hs
parent 08f12cde
......@@ -24,9 +24,7 @@ build_script:
- Setup build
- Setup test --show-details=streaming --test-option=--hide-successes
- Setup install
# hackage-repo-tool doesn't build on Windows:
# https://github.com/well-typed/hackage-security/issues/175
# - echo "" | cabal install hackage-repo-tool --allow-newer=Cabal,time --constraint="Cabal == 2.3.0.0"
- echo "" | cabal install hackage-repo-tool --allow-newer=Cabal,time --constraint="Cabal == 2.3.0.0"
- cd ..\cabal-testsuite
- ghc --make -threaded -i Setup.hs -package Cabal-2.3.0.0
- echo "" | ..\appveyor-retry cabal install --only-dependencies --enable-tests
......
......@@ -4,6 +4,10 @@ import Test.Cabal.Prelude
-- setup dependency on remote-setup-dep-3.0.
main = withShorterPathForNewBuildStore $ \storeDir ->
cabalTest $ do
-- TODO: Debug this failure on Windows.
skipIf =<< isWindows
skipUnless =<< hasNewBuildCompatBootCabal
withRepo "repo" $ do
r1 <- recordMode DoNotRecord $ cabalG' ["--store-dir=" ++ storeDir] "new-build" ["pkg:my-exe"]
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment