Skip to content

Slow down Tasty by limiting it to -j1 #261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 31, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
@@ -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: