testcover borkage

So,

If I just run ./Build testcover, it hangs at test 3 in t/basic.t

If I force usage of TAP::Harness API, I think this doesn't actually 
check the coverage, but because this is an environment variable and the 

  ./Build testcover --use-tap-harness
  191s later
  Can't open database /usr/local/code/hop_others/mb.alt/cover_db

  PERL5LIB=$OVER_THERE/Test-Harness-2.64/lib/:$PERL5LIB \
    ./Build testcover
  1906s later ... omg forever!

Now I have a coverage report for TAP::Parser and Module::Build?  And 
apparently better test coverage for TAP::Base than 
Module::Build::Base :-)

Probably the thing to do here is to tear out the usage of the 
Test::Harness API completely and maybe use PERL5OPT to -MDevel::Cover.  
The trick being that most of the M::B test suite that actually 
exercises M::B uses system().

The thing where I get coverage report of TAP::Parser and 
ExtUtils::CBuilder because they're in my $PERL5LIB is another thing, 
(and IIRC, known.)

So, anybody want to try this or should I put it in "the RT queue"? ;-)

--Eric
-- 
Moving pianos is dangerous.
Moving pianos are dangerous.
Buffalo buffalo buffalo buffalo buffalo buffalo buffalo.
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------