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
Describe the bug cabal test is slower than running cabal run tests when nothing has changed. This issue is exacerbated when using the new code generators feature, which makes cabal recompile the test suite on every invocation.
I suspect what is happening is the demo codegen drivers always emit new code even if it is bit-for-bit identical with old code, and that in turn triggers the rebuild -- i.e. it isn't a cabal issue, but just that the demo code is not very sophisticated. I also consider this somewhat low priority, in that it is not clear to me why someone would want to repeatedly rerun tests that are not recompiled, as they will continue to yield the same results?
Describe the bug
cabal test
is slower than runningcabal run tests
when nothing has changed. This issue is exacerbated when using the new code generators feature, which makes cabal recompile the test suite on every invocation.To Reproduce
Clone https://github.com/gbaz/cabal-doctest-demo.
Running the second time still recompiles the test suite.
Expected behavior
Cabal should not recompile the entire test suite when nothing has changed.
System information
The text was updated successfully, but these errors were encountered: