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

new-install fails on packages with tests/benchmarks unless --disable-tests/benchmarks is used #4855

Closed
fgaz opened this issue Oct 31, 2017 · 0 comments

Comments

@fgaz
Copy link
Member

fgaz commented Oct 31, 2017

For example, cabal new-install pandoc fails this assertion:

-- either a package is built inplace, or we are not attempting to
-- build any test suites or benchmarks (we never build these
-- for remote packages!)
. assert (elabBuildStyle == BuildInplaceOnly ||
Set.null elabStanzasAvailable)

This is easily fixed by setting the tests and benchmarks as disabled in every ElaboratedConfiguredPackage (or at an earlier stage) in CmdInstall.hs.

@fgaz fgaz self-assigned this Oct 31, 2017
@fgaz fgaz added the type: bug label Nov 3, 2017
@fgaz fgaz added this to the 2.2 milestone Nov 5, 2017
fgaz added a commit to fgaz/cabal that referenced this issue Nov 9, 2017
And error if they are explicitly enabled, so we never try to install
remote packages with tests and/or benchs.

Fixes haskell#4855
fgaz added a commit to fgaz/cabal that referenced this issue Nov 9, 2017
And error if they are explicitly enabled, so we never try to install
remote packages with tests and/or benchs.

Fixes haskell#4855
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant