-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Set test options via cabal.project #4039
Conversation
This means we can set the default properly for people using the project, and also set things more simply in the test workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
.github/workflows/test.yml
Outdated
# See https://github.com/ocharles/tasty-rerun/issues/22 for why we need | ||
# to include 'new' in the filters, since many of our test suites are in the | ||
# same package. | ||
run: | | ||
echo "TEST_OPTS=-j1 --rerun-update --rerun-filter failures,exceptions,new" >> $GITHUB_ENV | ||
echo 'cabal configure --test-options="--rerun-update --rerun-filter failures,exceptions,new"' >> cabal.project.local |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean this, which has the side effect of writing those options into cabal.project.local
echo 'cabal configure --test-options="--rerun-update --rerun-filter failures,exceptions,new"' >> cabal.project.local | |
cabal configure --test-options="--rerun-update --rerun-filter failures,exceptions,new" |
$ cabal configure --test-options="--rerun-update --rerun-filter failures,exceptions,new"
$ cat cabal.project.local
ignore-project: False
test-options: "--rerun-update"
"--rerun-filter"
"failures,exceptions,new"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's what I meant to type, just 🤦
This means we can set the default properly for people using the project, and also set things more simply in the test workflow.
The option setting in
hls-test-options
also seemed to be simply not working, for reasons I don't fully understand (but it seems likeNumThreads
is a special option.