On May 9, 2004, at 4:18 PM, Geoffrey Young wrote:
t/apache/errordoc.t 2 512 14 14 100.00% 1-14
I added that test recently and it passes for me on fedora. can you try
$ t/TEST t/apache/errordoc.t -v
and send that along (along with any relevant error_log messages). that all
tests fail probably mean that it's not picking up on a required
configuration thingy.
Same exact configuration I originally posted about, on same somewhat updated RH 8 box.
tty says:
t/TEST -httpd /tmp/ap/bin/httpd -apxs /tmp/ap/bin/apxs -v t/apache/errordoc.t
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl /home/sctemme/asf/perl-framework/t/TEST -httpd '/tmp/ap/bin/httpd' -apxs '/tmp/ap/bin/apxs' -v 't/apache/errordoc.t'
[ notice] mod_test_ssl.c requires Apache version 2, skipping.
[ notice] mod_test_pass_brigade.c requires Apache version 2, skipping.
[ notice] mod_test_apr_uri.c requires Apache version 2, skipping.
[ notice] mod_nntp_like.c requires Apache version 2, skipping.
[ notice] mod_input_body_filter.c requires Apache version 2, skipping.
[ notice] mod_client_add_filter.c requires Apache version 2, skipping.
make: Nothing to be done for `all'.
/tmp/ap/bin/httpd -d /home/sctemme/asf/perl-framework/t -f /home/sctemme/asf/perl-framework/t/conf/httpd.conf -D APACHE1 -D PERL_USEITHREADS
using Apache/1.3.31
waiting 60 seconds for server to start: .....
waiting 60 seconds for server to start: ok (waited 3 secs)
server eartha:8529 started
t/apache/errordoc....1..14
# Running under perl version 5.008 for linux
# Current time local: Mon May 10 09:56:05 2004
# Current time GMT: Mon May 10 16:56:05 2004
# Using Test.pm version 1.23
Use of uninitialized value in concatenation (.) or string at /home/sctemme/asf/perl-framework/Apache-Test/lib/Apache/TestRequest.pm line 185.
dubious
Test returned status 2 (wstat 512, 0x200)
DIED. FAILED tests 1-14
Failed 14/14 tests, 0.00% okay
Failed Test Stat Wstat Total Fail Failed List of Failed
------------------------------------------------------------------------ -------
t/apache/errordoc.t 2 512 14 14 100.00% 1-14
Failed 1/1 test scripts, 0.00% okay. 14/14 subtests failed, 0.00% okay.
[warning] server eartha:8529 shutdown
[ error] error running tests (please examine t/logs/error_log)
Access log:
127.0.0.1 - - [10/May/2004:09:56:05 -0700] "GET /index.html HTTP/1.0" 200 26
(Huh, only one entry for fourteen tests?)
Error log:
[Mon May 10 09:56:04 2004] [info] created shared memory segment #524292
[Mon May 10 09:56:04 2004] [notice] Apache/1.3.31 (Unix) configured -- resuming normal operations
[Mon May 10 09:56:04 2004] [info] Server built: May 8 2004 07:49:35
[Mon May 10 09:56:04 2004] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Mon May 10 09:56:07 2004] [info] removed PID file /home/sctemme/asf/perl-framework/t/logs/httpd.pid (pid=11234)
[Mon May 10 09:56:07 2004] [notice] caught SIGTERM, shutting down
(not exotic at all)
Rewrite log:
127.0.0.1 - - [10/May/2004:09:56:05 -0700] [eartha/sid#8093d54][rid#80c3edc/initial] (2) init rewrite engine with requested uri /index.html
127.0.0.1 - - [10/May/2004:09:56:05 -0700] [eartha/sid#8093d54][rid#80c3edc/initial] (1) pass through /index.html
(that's that same request we saw in access_log)
The single request for /index.html is the framework's ping to see if the server has started. It is not part of the errordoc tests, which suggests that these don't get to the server at all.
t/modules/cgi.t 46 4 8.70% 5-6 13-14
this just hangs for me, but there were some changes introduced recently that
may account for this - without looking at the change log it something about
STDERR IIRC.
Yes, it hangs for the longest time and then continues.
t/modules/expires.t 92 4 4.35% 13 21 33 45
fails for me as well.
it would be great to have the tests at 100% for current 1.3, 2.0, and 2.1.
if we can get it to that point I volunteer to be the project watchdog who
will pipe up if some commit causes the framework to suddenly fail (at least
on the platform I run, currently fedora). but until we get to 100% the
framework is kinda useless for RC testing as far as I'm concerned - "known
failures" don't really mean much for this kind of thing.
It has long been one of my desires to do an automated nightly build/test run on all three branches. As I get my lab set up here (which should happen in the next couple of weeks), I may be able to finally get that set up.
When I was testing a product based on httpd 2.0, I would keep a list of known failures (we had some patches that the framework didn't deal with) on our internal Wiki, so I would know that a test had been failing and I wouldn't have to analyze every failure to death every time. That was stuff like OpenSSL would put the email field name of a certificate DN in uppercase, and RSA SSLC would put it in lowercase. Or was it the other way around?
Anyway, it would be great to get something like that going on a daily basis. Kinda like an httpd project interpretation of Gump, like, Httpump.
S.
-- [EMAIL PROTECTED] http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
smime.p7s
Description: S/MIME cryptographic signature
