Skip to content

Commit

Permalink
cabal-validate: Reorder cli-tests
Browse files Browse the repository at this point in the history
The `cli-tests` are supposed to be ordered so that the quickest ones run
first. This is not the case, at least on my machine!
  • Loading branch information
9999years authored and Mikolaj committed Nov 27, 2024
1 parent 7386b00 commit 1498e59
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions cabal-validate/src/Main.hs
Original file line number Diff line number Diff line change
Expand Up @@ -325,15 +325,17 @@ libSuiteExtras opts = forM_ (extraCompilers opts) $ \compiler' ->
cliTests :: Opts -> IO ()
cliTests opts = do
-- These are sorted in asc time used, quicker tests first.

-- Only single job, otherwise we fail with "Heap exhausted"
timedCabalBin
opts
"cabal-install"
"test:long-tests"
( jobsArgs opts
"test:mem-use-tests"
( ["--num-threads", "1"]
++ tastyArgs opts
)

-- This doesn't work in parallel either.
-- This test-suite doesn't like concurrency
timedCabalBin
opts
"cabal-install"
Expand All @@ -342,16 +344,15 @@ cliTests opts = do
++ tastyArgs opts
)

-- Only single job, otherwise we fail with "Heap exhausted"
timedCabalBin
opts
"cabal-install"
"test:mem-use-tests"
( ["--num-threads", "1"]
"test:long-tests"
( jobsArgs opts
++ tastyArgs opts
)

-- This test-suite doesn't like concurrency
-- This doesn't work in parallel either.
timedCabalBin
opts
"cabal-install"
Expand Down

0 comments on commit 1498e59

Please sign in to comment.