-
Notifications
You must be signed in to change notification settings - Fork 842
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
first stack repl foo:test:bar
needs stack build --test --no-run-tests
#5213
Comments
Hi, while we are using |
qrilka
added a commit
that referenced
this issue
May 28, 2020
This partially fixes #5213 - starting a repl for an exe component doesn't appear to work for some reason
Many thanks for take care of this! |
This was referenced Jun 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
General summary/comments (optional)
If you starts a repl session in a test component that has dependencies, you need previously build test dependencies with
stack build --test --no-run-tests
This causes a bug in
hie-bios
, that usesstack repl
to get the ghc flags needed to start a ghc session in a ide (likehaskell-ide-engine
orghcide
): haskell/haskell-ide-engine#1564I guess
stack repl project:bench:benchname
will have the same behaviour.Steps to reproduce
In a simple stack project with a test component that has dependencies (
hspec
for example) i can reproduce the next cli session:This behaviour is not symmetric with
stack build project:test:testname
cause it builds test dependencies although you dont provide explicitly--tests
and imho is is a bit illogical that user wants to load a test component explicitly in the target but you have to provide--test --no-run-tests
to start the repl session.After a first
stack build --test
orstack build project:test:testname
, with the dependencies in the snapshot,stack repl project:test:testname
works until you delete the snapshot dir again.Expected
stack repl project:test:testname
should always build test dependencies if needed (and same for bench components)Stack version
Method of installation
The text was updated successfully, but these errors were encountered: