Joe Conway wrote:
> "make dcheck" is running now (although seems rather slow).
Yeah, most of those tests completely reset the environment for each
permutation. I thought about changing it to update back to the same
"visible" initial state each time, but it struck me that since this
would accumulate more and more dead tuples as the tests advanced, it
would exercise different code paths, so I've kinda got it in mind to
add the faster tests as *additional* tests rather than eliminating
the existing ones. I know they're way to slow to consider including
in the normal "make check" suite, but when (if?) we get a "test farm"
set up, this sort of thing seems like it would be in scope.
On the other hand, maybe we should have a "quick" set of dtester
tests and a more comprehensive one? I'm open to ideas.
-Kevin
