From 38672e030eaa68eddf195a027f56915edaa99597 Mon Sep 17 00:00:00 2001 From: Luke Lau Date: Fri, 31 Jul 2020 15:01:38 +0100 Subject: [PATCH] Slow down Tasty by limiting it to -j1 Fixes flakey CI builds. Turns out it was trying to run every single test in parallel at once, which is why when #247 added two extra tests it was just enough to push it over the limit and cause things to fail --- .circleci/config.yml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index f8eb5c5ada..453ef77811 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -42,7 +42,7 @@ defaults: &defaults - run: name: Build Testsuite without running it - command: stack -j 2 --stack-yaml=${STACK_FILE} build --test --no-run-tests + command: stack --stack-yaml=${STACK_FILE} build --test --no-run-tests no_output_timeout: 30m - store_artifacts: @@ -65,8 +65,11 @@ defaults: &defaults - run: name: Test haskell-language-server - # Tests MUST run with -j1, since multiple ghc-mod sessions are not allowed - command: stack -j 1 --stack-yaml=${STACK_FILE} test haskell-language-server --dump-logs + # Tasty by default will run all the tests in parallel. Which should + # work ok, but given that these CircleCI runners aren't the beefiest + # machine can cause some flakiness. So pass -j1 to Tasty (NOT Stack) to + # tell it to go slow and steady. + command: stack --stack-yaml=${STACK_FILE} test haskell-language-server --dump-logs --test-arguments="-j1" no_output_timeout: 120m - store_test_results: