httpd-test/perl-framework STATUS: -*-text-*-
Last modified at [$Date: 2002/03/09 05:22:48 $]
Stuff to do:
* finish the t/TEST exit code issue (ORed with 0x2C if
framework failed)
* change existing tests that frob the DocumentRoot (e.g.,
t/modules/
flood STATUS: -*-text-*-
Last modified at [$Date: 2003/07/01 20:55:12 $]
Release:
1.0: Released July 23, 2002
milestone-03: Tagged January 16, 2002
ASF-transfer: Released July 17, 2001
milestone-02: Tagged August 13, 2
Geoffrey Young wrote:
Geoffrey Young wrote:
committed. looking forward to hear about the odd parts.
the first thing that strikes me is that when I build mod_perl with
MP_APXS=/foo/bin/apxs then make && make test I get the dialogue asking me to
choose httpd and apxs binaries.
I don't think we want
Hi all,
I'm still working on getting my test environment in place using
Apache::Test. Recently, I added a vhost section to my extra.conf.in
file. The test servers fire up as I would expect on ports 8529 and 8530
when I run `t/TEST -start`. However, following the instructions on the
perl.apache.or
Can someone please confirm whether or not "apr_psprintf" is thread safe.
Thank you.
> Yes, thank you Geoff, I've noticed that too late. And my mail server was
> down most of the day :(
:)
>
> I think I have fixed these problems now.
>
> What bothers me is the call to default_httpd, which may pick a wrong
> server. So I've removed it. It is used in the interactive config, to
>
Donald Doane wrote:
> Can someone please confirm whether or not "apr_psprintf" is thread safe.
>
> Thank you.
sorry, wrong list. try [EMAIL PROTECTED]
--Geoff
[EMAIL PROTECTED] wrote:
geoff 2004/01/08 09:15:37
Modified:perl-framework/Apache-Test/lib/Apache Test.pm TestConfigC.pm
TestSSLCA.pm
Log:
fix have_apache_version(), have_min_apache_version(), and
have_min_module_version() to use proper numeric version stri
Okay, will do that, but it's called in
"flood_easy_reports::easy_process_stats()" and it seems APR
documentation implies it is not thread safe.
We use a modified version of "flood_easy_reports" and I'd like to
confirm whether or not its use is truly thread safe.
Geoffrey Young wrote:
Donald Do
>> -my $has_version = $module->VERSION || 0;
>> -return 1 if $has_version >= $version;
>> +return 1 if eval { $module->VERSION($version) };
>
>
> Are you sure you haven't dropped something here? why did you remove the
> comparison line?
becuase it's both wrong and unnecessa
Geoffrey Young wrote:
-my $has_version = $module->VERSION || 0;
-return 1 if $has_version >= $version;
+return 1 if eval { $module->VERSION($version) };
Are you sure you haven't dropped something here? why did you remove the
comparison line?
becuase it's both wrong and unnecessa
William McKee wrote:
Hi all,
I'm still working on getting my test environment in place using
Apache::Test. Recently, I added a vhost section to my extra.conf.in
file. The test servers fire up as I would expect on ports 8529 and 8530
when I run `t/TEST -start`. However, following the instructions o
Geoffrey Young wrote:
Yes, thank you Geoff, I've noticed that too late. And my mail server was
down most of the day :(
:)
I think I have fixed these problems now.
What bothers me is the call to default_httpd, which may pick a wrong
server. So I've removed it. It is used in the interactive config,
> Can you please run t/TEST -debug=trace and see which TestConfigData.pm
> is loaded? what's inside of it? May be the simple solution is not to
> load custom_config when running from inside modperl-2.0? I think that's
> the best solution.
I've already cleaned everything out for today, but I'll do
Geoffrey Young wrote:
Can you please run t/TEST -debug=trace and see which TestConfigData.pm
is loaded? what's inside of it? May be the simple solution is not to
load custom_config when running from inside modperl-2.0? I think that's
the best solution.
I've already cleaned everything out for today
15 matches
Mail list logo
