Skip to content

Full rebuild on test modification #120

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

Closed
nmattia opened this issue Apr 9, 2017 · 1 comment · Fixed by #227
Closed

Full rebuild on test modification #120

nmattia opened this issue Apr 9, 2017 · 1 comment · Fixed by #227

Comments

@nmattia
Copy link
Contributor

nmattia commented Apr 9, 2017

Not sure how to run the tests properly. So far I've been building the prop-compiled component. However it seems to imply a full rebuild every time I modify tests/Properties.hs. I suspect the reason is because prop-compiled doesn't use bytestring as a library but rather lists the source files as its own in hs-source-dirs: . tests. For some reason, some other packages (regex-base, text, ansi-wl-pprint, ...) are recompiled as well. This takes up a whole minute for every change I make in the tests. Am I missing a simple way to run them that doesn't involve compiling?

EDIT:
disclaimer (don't shoot): I'm using stack build bytestring:prop-compiled

@hvr
Copy link
Member

hvr commented Apr 22, 2017

Well, bytestring is a bit special as it's a package super low in the dependency graph, and this results in its testsuites running into cyclic dependency issues (i.e. text depends on the bytestring package). This is a rather long-standing finicky issue and affects mostly core packages such as bytestring which everyone else depends upon, see haskell/cabal#3824 (comment) for a recent analysis. And yes, the reason you see modules being compiled multiple times is that the testsuites don't depend upon bytestring, but rather compile their own copies.

@sjakobi sjakobi linked a pull request Jun 25, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants