The following tests are all sh scripts that won't work on win32, we should
exclude on non-sh supporting platforms;
apache\acceptpathinfo.t 36 10 27.78% 9-10, 21-24, 33-36
The following test looks like we didn't follow our have apxs test results
(we can't compile modules on win32 right at this instant) before we try
an echo_post_chunk request;
apache\chunkinput.t92 22.22% 2-3
This looks like the same problem again, we never built echo_post before
attempting to run the contentlength.t tests;
apache\contentlength.t203 15.00% 2, 6, 10
I'm entirely unclear what is happening on these two tests, however;
apache\limits.t 102 20.00% 9-10
# Testing LimitRequestBody; should fail
# Chunked transfer-encoding enabled
# testing : Test #9
# expected: 413
# received: 500
not ok 9
# Failed test 9 in apache\limits.t at line 112 fail #2
# Server response:
# 500 (Internal Server Error) EOF
# Client-Date: Sat, 22 Jun 2002 20:47:14 GMT
#
#
#
# Testing LimitRequestBody; should fail
# Chunked transfer-encoding disabled
#lwp request:
#GET http://localhost:8529/apache/limits/ HTTP/1.0
#User-Agent: libwww-perl/5.65
#Content-Type: text/plain
#X-Subtest: 10
#
#aaa[...sparing
you lots of 'a's in the lwp=2 output...
a
#server response:
#500 (Internal Server Error) EOF instead of reponse status line
#Content-Length: 0
#Client-Date: Sat, 22 Jun 2002 20:47:14 GMT
#X-Content-Length-Note: added by Apache::TestRequest
#
#
# testing : Test #10
# expected: 413
# received: 500
not ok 10
# Failed test 10 in apache\limits.t at line 123 fail #2
# Server response:
# 500 (Internal Server Error) EOF instead of reponse status line
# Content-Length: 0
# Client-Date: Sat, 22 Jun 2002 20:47:14 GMT
# X-Content-Length-Note: added by Apache::TestRequest
This one is just plain silly, looks like a semantics error...
modules\include.t 516 11.76% 46-51
ok 36
ok 37 # Skipping XBitHack tests on this platform
ok 38 # Skipping XBitHack tests on this platform
ok 39 # Skipping XBitHack tests on this platform
ok 40 # Skipping XBitHack tests on this platform
ok 41 # Skipping XBitHack tests on this platform
ok 42 # Skipping XBitHack tests on this platform
ok 43 # Skipping XBitHack tests on this platform
ok 44 # Skipping XBitHack tests on this platform
ok 45 # Skipping XBitHack tests on this platform
FAILED tests 46-51
Failed 6/51 tests, 88.24% okay (-9 skipped tests: 36 okay, 70.59%)
Since when is a skip == failure :-?
I won't bother reporting our failures in ssl\*.t for the moment till I get
a handle on what ssl perl module errors are going on.
So if someone who groks this all would add [and fix the existing borked]
'skipping' statuses to these tests, or share some observation about what
is up with the limits.t test, I would be most appreciative.
Bill
