I was doing some refactoring for ghc-6.6 (not my default compiler),
and when I was done I thought I'd just run, 'make disttest' so I could
see if I pass the tests before taking the time to record everything.

disttest makes darcs check out your current working directory to a
temp location and then run configure on it.  This made the tests use
the wrong version of ghc (6.6 is not the version of ghc that is in my
path).

I'm filing this bug because Trent asked me to make note of it so he
can look at it later.

Thanks!
Jason

Running configure is the point of disttest, which doesn't check out a clean copy
of the source before running.  If you wanted to just run the tests, you could
have just done that.

That said, some docs or maybe a better name would help?

What target should be run to do all the tests, witnesses, unit, the shell tests?

On Mon, Nov 03, 2008 at 12:02:07AM -0000, Jason Dagit wrote:
> What target should be run to do all the tests, witnesses, unit, the shell tests?

We don't have a target to do that, but you can do it with

make test_unit disttest

and yes it will rerun configure, because that's the only way to do the
witnesses test (and because disttest is designed to test, among other
things, that the configure script works).
-- 
David Roundy
http://www.darcs.net

Trent,

Do you have the information now to look into this?  What we need is a way to run
the same things as disttest minus the run of configure that changes options? 
For example, we shouldn't need to re-run configure, just flip the switch so that
GADT_WITNESSES is defined and we make clean.  And David obviously wants to keep
disttest as a way of doing the things it currently does so we'd need a new name
I suppose.

I'm assigning it to you for now, but if you change your mind about wanting to
work on it go ahead on and mark it unassigned.

Jason

Now moot due to the Cabal switchover