Skip to content
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

Assertion failed when adding tests: False to ~/.cabal/config #5270

Open
gelisam opened this issue Apr 18, 2018 · 1 comment
Open

Assertion failed when adding tests: False to ~/.cabal/config #5270

gelisam opened this issue Apr 18, 2018 · 1 comment
Labels
cabal-install: nix-local-build type: assertion-fail NB: assertions are only enabled in devel-builds type: bug

Comments

@gelisam
Copy link
Collaborator

gelisam commented Apr 18, 2018

The default ~/.cabal/config contains the commented out line tests: False, implying that this is the default, and yet when uncommenting that line and building a project which contains tests with cabal-custom new-build all, I get an assertion error:

$ cabal-custom new-build all
Build profile: -w ghc-8.2.2 -O1
In order, the following will be built (use -v for more details):
Assertion failed
CallStack (from HasCallStack):
assert, called at ./Distribution/Client/ProjectPlanning.hs:240:5 in cabal-install-2.3.0.0-inplace:Distribution.Client.ProjectPlanning

I believe this is yet another consequence of the fact that the default is neither to enable nor to disable the tests, but a third option.

@hvr hvr added the type: assertion-fail NB: assertions are only enabled in devel-builds label Oct 27, 2018
@Mikolaj
Copy link
Member

Mikolaj commented Mar 22, 2022

This may be related to #6006.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cabal-install: nix-local-build type: assertion-fail NB: assertions are only enabled in devel-builds type: bug
Projects
None yet
Development

No branches or pull requests

3 participants