On Thu, May 20, 2004 at 08:29:33PM -0700, Stas Bekman wrote:
> Please show us the verbose trace:
>
> t/TEST -trace=debug
>
> including the part where you completed the interactive questions, and it
> brought you back to interactive config again.
Got the latest version from CVS again and this time received the
following message when running `perl Makefile.PL':
generating script t/TEST
Checking if your kit is complete...
Warning: the following files are missing in your kit:
META.yml
Please inform the author.
Writing Makefile for Apache::Test
The trace is attached. Note that this test was performed on a different
system which apparently did not have the location of my server cached so
I had to type it in. I still saw the same looping behavior.
All tests pass if I run `t/TEST -httpd /usr/local/apache/bin/httpd'.
William
--
Knowmad Services Inc.
http://www.knowmad.com
[EMAIL PROTECTED]:~/perl/modperl-2.0/Apache-Test$ t/TEST -trace=debug
setting ulimit to allow core files
ulimit -c unlimited; /usr/local/bin/perl
/home/william/perl/modperl-2.0/Apache-Test/t/TEST -trace=debug
trying to load custom config data
loading custom config path '/home/william/.apache-test/Apache/TestConfigData.pm'
can't figure out Apache revision, from string: '', using a non-existing
revision 0
generating conf/mime.types
generating htdocs/index.html
Will 'Include' /home/william/perl/modperl-2.0/Apache-Test/t/conf/extra.conf
config file
generating conf/extra.conf from
/home/william/perl/modperl-2.0/Apache-Test/t/conf/extra.conf.in
generating conf/httpd.conf
generating conf/apache_test_config.pm
saving config data to apache_test_config.pm
trying to load custom config data
can't figure out Apache revision, from string: '', using a non-existing
revision 0
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/mime.types
unlink /home/william/perl/modperl-2.0/Apache-Test/t/htdocs/index.html
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/apache_test_config.pm
unlink
/home/william/perl/modperl-2.0/Apache-Test/t/logs/apache_runtime_status.sem: No
such file or directory
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/httpd.conf
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/extra.conf
rmdir /home/william/perl/modperl-2.0/Apache-Test/t/logs
rmdir /home/william/perl/modperl-2.0/Apache-Test/t/htdocs
We are now going to configure the Apache-Test framework.
This configuration process needs to be done only once.
First we need to know where the 'httpd' executable is located.
If you have more than one Apache server is installed, make sure
you supply the path to the one you are going to use for testing.
You can always override this setting at run time via the '-httpd'
option. For example:
% t/TEST -httpd /path/to/alternative/httpd
or via the environment variable APACHE_TEST_HTTPD. For example:
% APACHE_TEST_HTTPD=/path/to/alternative/httpd t/TEST
If for some reason you want to skip the test suite, type: skip
Please provide a full path to 'httpd' executable:
[] /usr/local/apache/bin/httpd
Next we need to know where the 'apxs' script is located. This script
provides a lot of information about the apache installation, and makes
it easier to find things. However it's not available on all platforms,
therefore it's optional.
If you don't have it installed it's not a problem. Just press Enter.
Notice that if you have Apache 2.x installed that script could be
called as 'apxs2'.
If you have more than one Apache server is installed, make sure you
supply the path to the apxs script you are going to use for testing.
You can always override this setting at run time via the '-apxs'
option. For example:
% t/TEST -apxs /path/to/alternative/apxs
or via the environment variable APACHE_TEST_APXS. For example:
% APACHE_TEST_APXS=/path/to/alternative/apxs t/TEST
Please provide a full path to (optional) 'apxs' executable:
[]
Found custom config '/home/william/.apache-test/Apache/TestConfigData.pm'
Writing custom config /home/william/.apache-test/Apache/TestConfigData.pm
rerunning '/usr/local/bin/perl
/home/william/perl/modperl-2.0/Apache-Test/t/TEST -trace=debug' with new config
opts
trying to load custom config data
loading custom config path '/home/william/.apache-test/Apache/TestConfigData.pm'
can't figure out Apache revision, from string: '', using a non-existing
revision 0
generating conf/mime.types
generating htdocs/index.html
Will 'Include' /home/william/perl/modperl-2.0/Apache-Test/t/conf/extra.conf
config file
generating conf/extra.conf from
/home/william/perl/modperl-2.0/Apache-Test/t/conf/extra.conf.in
generating conf/httpd.conf
generating conf/apache_test_config.pm
saving config data to apache_test_config.pm
trying to load custom config data
can't figure out Apache revision, from string: '', using a non-existing
revision 0
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/mime.types
unlink /home/william/perl/modperl-2.0/Apache-Test/t/htdocs/index.html
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/apache_test_config.pm
unlink
/home/william/perl/modperl-2.0/Apache-Test/t/logs/apache_runtime_status.sem: No
such file or directory
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/httpd.conf
unlink /home/william/perl/modperl-2.0/Apache-Test/t/conf/extra.conf
rmdir /home/william/perl/modperl-2.0/Apache-Test/t/logs
rmdir /home/william/perl/modperl-2.0/Apache-Test/t/htdocs
We are now going to configure the Apache-Test framework.
This configuration process needs to be done only once.
First we need to know where the 'httpd' executable is located.
If you have more than one Apache server is installed, make sure
you supply the path to the one you are going to use for testing.
You can always override this setting at run time via the '-httpd'
option. For example:
% t/TEST -httpd /path/to/alternative/httpd
or via the environment variable APACHE_TEST_HTTPD. For example:
% APACHE_TEST_HTTPD=/path/to/alternative/httpd t/TEST
If for some reason you want to skip the test suite, type: skip
Please provide a full path to 'httpd' executable:
[]
