#11737: Make validate --testsuite-only behave correctly w.r.t. bindisttest -------------------------------------+------------------------------------- Reporter: goldfire | Owner: Type: feature request | Status: new Priority: normal | Milestone: Component: Build System | Version: 8.1 Resolution: | Keywords: Operating System: Unknown/Multiple | Architecture: | Unknown/Multiple Type of failure: None/Unknown | Test Case: Blocked By: | Blocking: Related Tickets: | Differential Rev(s): Wiki Page: | -------------------------------------+------------------------------------- Comment (by goldfire): Replying to [comment:1 thomie]:
I think it would be confusing if `./validate --testsuite-only` didn't run the tests in the same way as `./validate`.
Point well-taken.
Maybe one of the following solutions can serve you already? Instead of
`./validate --testsuite-only`, run:
* `make test THREADS=<n>`. It doesn't use the binary distribution.
I thought of this but wasn't sure it would run the same set of tests in the same way.
or * `./validate --no-clean`. It will call `make`, which should be a no- op, then recreate the binary distribution, and then call `make test BINDIST=YES` for you.
This wouldn't have been a no-op, because I edited the GHC source code. So it would have rebuilt everything from stage1 on. Perhaps the answer I'm looking for is `validate --no-clean --lax-dependencies` or `validate --no- clean --stage-2`. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/11737#comment:2 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler