You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
Uh oh!
There was an error while loading. Please reload this page.
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 modifytests/Properties.hs
. I suspect the reason is becauseprop-compiled
doesn't usebytestring
as a library but rather lists the source files as its own inhs-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
The text was updated successfully, but these errors were encountered: