On Oct 5, 2004, at 12:53 PM, Geoffrey Young wrote:
yeah, I think that's all the required up front pieces. authors still
need
to configure Devel::Cover over in httpd.conf land, but there's not
much we
can do from a makefile to help with that.
I think we're good to go, then.
Regards,
David
David Wheeler wrote:
> On Oct 5, 2004, at 12:43 PM, Geoffrey Young wrote:
>
>> no, it is required. but only cvs currently supports -one-process as an
>> option - earlier versions will explode.
>
>
> Okay. So I just added this to the testcover action:
>
> local $ENV{APACHE_TEST_EXTRA_ARGS
On Oct 5, 2004, at 12:43 PM, Geoffrey Young wrote:
no, it is required. but only cvs currently supports -one-process as an
option - earlier versions will explode.
Okay. So I just added this to the testcover action:
local $ENV{APACHE_TEST_EXTRA_ARGS} = "-one-process";
Is that all it needs?
Regar
David Wheeler wrote:
> On Oct 5, 2004, at 12:36 PM, Geoffrey Young wrote:
>
>> somewhere in here it looks like -one-process is missing, though I
>> wouldn't
>> know where it would go.
>
>
> I'll put it in, though it isn't needed if you use A-T in CVS, eh?
no, it is required. but only cvs cur
On Oct 5, 2004, at 12:36 PM, Geoffrey Young wrote:
somewhere in here it looks like -one-process is missing, though I
wouldn't
know where it would go.
I'll put it in, though it isn't needed if you use A-T in CVS, eh?
you're the only one with commit access who uses or understand
Module::Build,
so g
> +my $atdir = $self->localize_file_path("$ENV{HOME}/.apache-test");
> +local $Test::Harness::switches=
> +local $Test::Harness::Switches=
> +local $ENV{HARNESS_PERL_SWITCHES} = "-MDevel::Cover=+inc,'$atdir'";
somewhere in here it looks like -one-process is missing, though
On Oct 5, 2004, at 11:51 AM, Geoffrey Young wrote:
basically it goes into $HOME because it stores the A-T preferences for
a
specific user. but this is all part of the endless 'sticky
preferences' foo
that I really don't want to be associated with ;) lots of to and fro
in the
httpd-test archive
On Oct 5, 2004, at 11:51 AM, Geoffrey Young wrote:
basically it goes into $HOME because it stores the A-T preferences for
a
specific user. but this is all part of the endless 'sticky
preferences' foo
that I really don't want to be associated with ;) lots of to and fro
in the
httpd-test archive
David Wheeler wrote:
> On Oct 5, 2004, at 11:32 AM, Geoffrey Young wrote:
>
>>> Ah, cool. But $(HOME) doesn't correspond to ~/ here, does it?
>>
>>
>> yeah - it's equivalent to $ENV{HOME} in make-land. I guess there is
>> always
>> the danger that $HOME isn't populated, but internally A-T uses
On Tue, Oct 05, 2004 at 11:32:23AM -0700, David Wheeler wrote:
> On Oct 5, 2004, at 11:25 AM, Paul Johnson wrote:
>
> >I wonder whether we shouldn't try to standardise the target name before
> >it's too late to do so. Module::Build uses covertest, I've always used
> >cover, and Geoff has just us
On Oct 5, 2004, at 11:32 AM, Geoffrey Young wrote:
Ah, cool. But $(HOME) doesn't correspond to ~/ here, does it?
yeah - it's equivalent to $ENV{HOME} in make-land. I guess there is
always
the danger that $HOME isn't populated, but internally A-T uses
$ENV{HOME}
when it generates the .apache-test
>>test-cover ::
>> @cover -delete
>> @HARNESS_PERL_SWITCHES=-MDevel::Cover=+inc,$(HOME)/.apache-test
>>APACHE_TEST_EXTRA_ARGS=-one-process $(MAKE) test
>> @cover
>
>
> I wonder whether we shouldn't try to standardise the target name before
> it's too late to do so. Module::Build
>> - HARNESS_PERL_SWITCHES gets Devel::Cover started
>
>
> Module::Build's testcover target already does this.
:)
>
>> - +inc,$(HOME)/.apache-test keeps coverage away from generated A-T
>> files,
>> which isn't required
>
>
> Ah, cool. But $(HOME) doesn't correspond to ~/ here, does it?
On Oct 5, 2004, at 11:25 AM, Paul Johnson wrote:
I wonder whether we shouldn't try to standardise the target name before
it's too late to do so. Module::Build uses covertest, I've always used
cover, and Geoff has just used test-cover.
Actually, Module::Build uses "testcover".
I'm not overly concer
On Tue, Oct 05, 2004 at 02:08:25PM -0400, Geoffrey Young wrote:
> David Wheeler wrote:
> >
> > Perhaps I should add support for Module::Build's "covertest" action to
> > Apache::TestMB...just tell me what it needs to do.
>
> I think that all Apache::TestMB would need to do is add a make target t
On Oct 5, 2004, at 11:08 AM, Geoffrey Young wrote:
I think that all Apache::TestMB would need to do is add a make target
that
looks like this:
test-cover ::
@cover -delete
@HARNESS_PERL_SWITCHES=-MDevel::Cover=+inc,$(HOME)/.apache-test
APACHE_TEST_EXTRA_ARGS=-one-process $(MAKE) t
David Wheeler wrote:
> On Oct 2, 2004, at 2:30 PM, Geoffrey Young wrote:
>
>> I started to maintain Apache-Test skeletons, but I never quite got
>> them up
>> to speed. give me a few days and I'll roll a tarball with a test-cover
>> target so that folks can have an entire working example of the
On Tue, Oct 05, 2004 at 11:27:01AM -0400, Geoffrey Young wrote:
> as promised, here is a tarball that includes a 'test-cover' target.
>
> http://perl.apache.org/~geoff/Apache-Test-with-Devel-Cover.tar.gz
>
> it's made a little more complex than it needs to be because of version
> restrictions:
Geoffrey Young wrote:
>>[ Just before sending this I notice Geoff has recommended something
>>better, but I'll send this too as another WTDI. ]
>
>
> cool :)
>
> I started to maintain Apache-Test skeletons, but I never quite got them up
> to speed. give me a few days and I'll roll a tarball w
On Oct 2, 2004, at 2:30 PM, Geoffrey Young wrote:
I started to maintain Apache-Test skeletons, but I never quite got
them up
to speed. give me a few days and I'll roll a tarball with a test-cover
target so that folks can have an entire working example of the way I
would
do it.
Perhaps I should a
On Oct 2, 2004, at 12:36 PM, Geoffrey Young wrote:
we use Apache-Test, which starts the server, runs the tests, and shuts
down
the server again.
When I last talked with you about Apache-Test, I seem to recall that
you said that it was restricted to running the tests serially. Is this
still tr
> [ Just before sending this I notice Geoff has recommended something
> better, but I'll send this too as another WTDI. ]
cool :)
I started to maintain Apache-Test skeletons, but I never quite got them up
to speed. give me a few days and I'll roll a tarball with a test-cover
target so that folk
Kevin Scaldeferri wrote:
>
> On Oct 2, 2004, at 12:36 PM, Geoffrey Young wrote:
>
>>>
>>
>> we use Apache-Test, which starts the server, runs the tests, and shuts
>> down
>> the server again.
>
>
>
> When I last talked with you about Apache-Test, I seem to recall that you
> said that it was
On Sat, Oct 02, 2004 at 11:20:05AM -0700, Kevin Scaldeferri wrote:
> On Sep 21, 2004, at 1:30 PM, Kevin Scaldeferri wrote:
> >
> >So, I don't expect anyone to try to figure out this stack trace stuff,
> >but I'm curious if other people have seen stability problems like
> >this? Alternatively, i
> if you haven't investigated Apache-Test yet, I would. our custom make
> target look like this:
I forgot to add some A-T specific stuff :)
t/conf/modperl_extra.pl:
if ($ENV{HARNESS_PERL_SWITCHES}) {
eval {
require Devel::Cover;
Devel::Cover->import('+ignore' => 't/response/'
Kevin Scaldeferri wrote:
>
> On Sep 21, 2004, at 1:30 PM, Kevin Scaldeferri wrote:
>
>>
>> So, I don't expect anyone to try to figure out this stack trace stuff,
>> but I'm curious if other people have seen stability problems like
>> this? Alternatively, if someone can tell me the exact logist
On Sep 21, 2004, at 1:30 PM, Kevin Scaldeferri wrote:
So, I don't expect anyone to try to figure out this stack trace stuff,
but I'm curious if other people have seen stability problems like
this? Alternatively, if someone can tell me the exact logistics of
how they get the coverage out in the
Hi,
On Tue, 21 Sep 2004, Kevin Scaldeferri wrote:
> This patch gets rid of that error, and now my server starts up. I
> admit that I don't really understand its magic (eval 'BEGIN{1}'???),
> but it's progress.
What you call magic actually forces perl to run function 'runops_cover'
(see Cover
On Sep 21, 2004, at 2:58 AM, [EMAIL PROTECTED] wrote:
On Mon, 20 Sep 2004, Kevin Scaldeferri wrote:
The current version of Devel::Cover asserts that running it on a
mod_perl server ought to be as simple as adding 'use Devel::Cover' to
your startup script. However, when I do this, I get the followi
Hi,
On Mon, 20 Sep 2004, Kevin Scaldeferri wrote:
> The current version of Devel::Cover asserts that running it on a
> mod_perl server ought to be as simple as adding 'use Devel::Cover' to
> your startup script. However, when I do this, I get the following
> failure:
>
> Syntax error on lin
Kevin Scaldeferri wrote:
On Sep 20, 2004, at 4:24 PM, Randy W. Sims wrote:
Kevin Scaldeferri wrote:
(As an aside, can anyone recommend an archive of this list with good
search capability? I'm sure there've been more than 4 postings in
the past that should match "devel::cover mod_perl")
If your
The current version of Devel::Cover asserts that running it on a
mod_perl server ought to be as simple as adding 'use Devel::Cover' to
your startup script. However, when I do this, I get the following
failure:
Syntax error on line 1225 of /home/kevin/.../conf/httpd.conf:
Can't use an undefined
32 matches
Mail list logo
