> No, not when I run the example out of the box - I had to move the > PerlPassEnv directives to extra.conf.in and rebuild (this makes sense, > though, as extra.conf is processed before modperl_extra.pl, while > extra.last.conf is processed after - perhaps you fixed your local copy and > haven't uploaded that change to the published version?)
yes :) but I thought I did it before I sent you the initial email. I guess not. anyway, what's up there now should not have that specific issue... > > The test case in the demo doesn't contain the problem I'm having, though. > Tests that aren't of the very specific write-the-request write-the-response > in t/apache and t/response/TestApache work fine for me, too. well, I don't understand the exact issue then. if you can adjust the (freshly uploaded) tarball such that it exhibits your problem in a very minimal sense I'll take a look. maybe that will help. > > I have it on the run, though - It appears to be an interaction between > TestMB and D::C. I have gotten it to give me correct results a couple of > times - I'm currently trying to isolate/replicate the exact settings that > yield correct results. well, I can't speak to TestMB.pm or Module::Build in general. if you shift to the standard MakeMaker interface of 'make testcover' I will be in a better position to help you. if you still have issues we can isolate and (hopefully) fix them, then ping david about making the required TestMB.pm changes. > > One problem which I've isolated is that running ./Build testcover overrides > the select/ignore settings specified via import. hmm. well, one thing at a time. all of Apache-Test was developed using MakeMaker, with Module::Build support strapped on far after the fact. so, let's figure out what D::C issues there are with the "standard" interface and see if we can't get it working there first. then we'll make the Module::Build people happy :) > > More info in a bit.... > > (This is fun, right? right?) yes, of course. was there ever any question? ;) --Geoff
