Anyway - trying to learn howto work with test.
server loopback:8552 listening (proxy_https_http)
t/apache/server_name_port....Can't call method "parse" on an undefined
value at (eval 18) line 1.
t/apache/server_name_port....dubious
Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-84
Failed 84/84 tests, 0.00% okay
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
t/apache/server_name_port.t 255 65280 84 168 200.00% 1-84
Failed 1/1 test scripts, 0.00% okay. 84/84 subtests failed, 0.00% okay.
Cannot find anything in t/errors/log related to the test - even though
there are 389 lines generated in the error_log
perl is not my strong suit.
in t/apache/server_port_name.t the only code I find with 'parse; in it is:
my $response = HTTP::Response->parse($response_data);
if (! defined $response) {
die "HTTP::Response->parse failed";
}
This does not look like line 1 either. Neither does it look like line 18
(whatever eval 18 means).
Lastly, why is it counting double?
On Tue, Aug 5, 2014 at 4:29 PM, Michael Felt <[email protected]> wrote:
> Anyway, I figured out a way to get it to load and run the tests with a
> newer version of ssl (0.9.8za) compared to an AIX build version from 2009.
>
> Not as big a difference as I had hoped - just 5 tests better in
> t/ssl/proxy.t
>
> So, curious if others working with AIX are showing similiar errors as I am
> - or if I need to look more carefully at how I am building for AIX.
> NEW SSL (openssl.0.9.8.za) results
>
> Failed Test Stat Wstat Total Fail Failed List of Failed
>
> -------------------------------------------------------------------------------
> t/apache/server_name_port.t 255 65280 84 168 200.00% 1-84
> t/modules/proxy.t 17 2 11.76% 9-10
> t/protocol/echo.t 255 65280 8 16 200.00% 1-8
> t/protocol/nntp-like.t 255 65280 10 20 200.00% 1-10
> t/security/CVE-2005-2700.t 2 1 50.00% 1
> t/security/CVE-2009-3555.t 255 65280 4 8 200.00% 1-4
> t/ssl/basicauth.t 3 2 66.67% 2-3
> t/ssl/env.t 30 23 76.67% 1-8 16-30
> t/ssl/extlookup.t 4 4 100.00% 1-4
> t/ssl/fakeauth.t 3 2 66.67% 2-3
> t/ssl/headers.t 3 3 100.00% 1-3
> t/ssl/pr12355.t 10 8 80.00% 1-8
> t/ssl/pr43738.t 4 4 100.00% 1-4
> t/ssl/proxy.t 172 113 65.70% 60-172
> t/ssl/require.t 10 5 50.00% 2 5-7 9
> t/ssl/varlookup.t 73 73 100.00% 1-73
> t/ssl/verify.t 3 1 33.33% 2
> 17 tests and 40 subtests skipped.
> Failed 17/109 test scripts, 84.40% okay. 347/4661 subtests failed, 92.56%
> okay.
>
> OLD openssl results
> openssl.base 0.9.8.1101 C F Open Secure Socket Layer
>
> Failed Test Stat Wstat Total Fail Failed List of Failed
>
> -------------------------------------------------------------------------------
> t/apache/server_name_port.t 255 65280 84 168 200.00% 1-84
> t/modules/proxy.t 17 2 11.76% 9-10
> t/protocol/echo.t 255 65280 8 16 200.00% 1-8
> t/protocol/nntp-like.t 255 65280 10 20 200.00% 1-10
> t/security/CVE-2005-2700.t 2 1 50.00% 1
> t/security/CVE-2009-3555.t 255 65280 4 8 200.00% 1-4
> t/ssl/basicauth.t 3 2 66.67% 2-3
> t/ssl/env.t 30 23 76.67% 1-8 16-30
> t/ssl/extlookup.t 4 4 100.00% 1-4
> t/ssl/fakeauth.t 3 2 66.67% 2-3
> t/ssl/headers.t 3 3 100.00% 1-3
> t/ssl/pr12355.t 10 8 80.00% 1-8
> t/ssl/pr43738.t 4 4 100.00% 1-4
> t/ssl/proxy.t 172 118 68.60% *3-7* 60-172
> t/ssl/require.t 10 5 50.00% 2 5-7 9
> t/ssl/varlookup.t 73 73 100.00% 1-73
> t/ssl/verify.t 3 1 33.33% 2
> 17 tests and 40 subtests skipped.
> Failed 17/109 test scripts, 84.40% okay. 352/4661 subtests failed, 92.45%
> okay.
>
>
> On Mon, Aug 4, 2014 at 6:05 PM, Michael Felt <[email protected]> wrote:
>
>> So, I figured out how to make a new libssl and libcrypt - as a way to
>> "fix" a lot of failed tests, and as I would rather leave the original files
>> in /usr/lib and add new ones in /opt/lib - what flag am I missing (and
>> should I have asked this in "users") so the the modules ALSO use the same
>> LIBPATH. I would have expected them to have the same as the core.
>> core uses: /opt/lib:/usr/vac/lib:/usr/lib:/lib
>> as expected while the modules (more specifically, mod_ssl) does not look
>> /opt/lib at all!
>> mod_ssl.so uses: /usr/include/openssl/lib:/usr/vac/lib:/usr/lib:/lib
>> Note: there is no such directory /usr/include/openssl/lib - configure (or
>> libtool) seems to be inventing that.
>>
>> DUMP comand output - complete.
>>
>> root@x093:[/]dump -H /opt/httpd/sbin/httpd
>>
>> /opt/httpd/sbin/httpd:
>>
>> ***Loader Section***
>> Loader Header Information
>> VERSION# #SYMtableENT #RELOCent LENidSTR
>> 0x00000001 0x0000041e 0x00000c88 0x00000095
>>
>> #IMPfilID OFFidSTR LENstrTBL OFFstrTBL
>> 0x00000007 0x0000f950 0x000054dc 0x0000f9e5
>>
>>
>> ***Import File Strings***
>> INDEX PATH BASE
>> MEMBER
>> 0
>> /opt/lib:/usr/vac/lib:/usr/lib:/lib
>> 1 libpcre.a
>> libpcre.so.1
>> 2
>> libaprutil-1.so
>> 3
>> libapr-1.so
>> 4 libpthread.a
>> shr_xpg5.o
>> 5 libc.a
>> shr.o
>> 6 librtl.a
>> shr.o
>> root@x093:[/]dump -H /opt/httpd/lib*/mod_ssl*
>>
>> /opt/httpd/libexec/mod_ssl.so:
>>
>> ***Loader Section***
>> Loader Header Information
>> VERSION# #SYMtableENT #RELOCent LENidSTR
>> 0x00000001 0x000001c4 0x00000451 0x00000083
>>
>> #IMPfilID OFFidSTR LENstrTBL OFFstrTBL
>> 0x00000005 0x00005e4c 0x00002128 0x00005ecf
>>
>>
>> ***Import File Strings***
>> INDEX PATH BASE
>> MEMBER
>> 0
>> /usr/include/openssl/lib:/usr/vac/lib:/usr/lib:/lib
>>
>> 1 libssl.a
>> libssl.so.0.9.8
>> 2 libcrypto.a
>> libcrypto.so.0.9.8
>> 3 libc.a
>> shr.o
>> 4
>> ..
>>
>>
>>
>>
>> On Sun, Aug 3, 2014 at 4:35 PM, Michael Felt <[email protected]> wrote:
>>
>>> Thanks. So, when the t/TEST has a line with NOK: in it, there should be
>>> an error: in there I expect.
>>> FYI: most of what I am seeing are ssl related, but the vanilla ssh on
>>> AIX 5.3 TL7 is from 2009, so that is probably not surprising. (Going to
>>> investigate "inserting" a new openssl library and see if sshd still works
>>> as well as fewer t/TEST errors.)
>>>
>>>
>>> On Sun, Aug 3, 2014 at 3:03 PM, Eric Covener <[email protected]> wrote:
>>>
>>>> On Sun, Aug 3, 2014 at 7:50 AM, Michael Felt <[email protected]> wrote:
>>>> > A couple of time I have gotten started with using test from Apache.
>>>> >
>>>> > Just to be clear about how I am starting I use svn to get the latest
>>>> sources
>>>> > and have test and test/ApacheTest from
>>>> >
>>>> > ./svn/bin/jsvn checkout
>>>> > http://svn.apache.org/repos/asf/httpd/test/framework/trunk
>>>> > /data/prj/apache/httpd/test
>>>> > echo Apache-Test starting
>>>> > ./svn/bin/jsvn checkout
>>>> > http://svn.apache.org/repos/asf/perl/Apache-Test/trunk
>>>> > /data/prj/apache/httpd/test/Apache-Test
>>>>
>>>> I only checkout
>>>> https://svn.apache.org/repos/asf/httpd/test/framework/trunk and my SVN
>>>> client fetches the other as an external (I think, it just works)
>>>>
>>>> > 1) should Apache-Test be a subdirectory (does "test" recognize that
>>>> and use
>>>> > it on some way - or is that a separate test intended only/mainly for
>>>> > mod_perl). Apache-Test as a project page does not say much.
>>>>
>>>> It's for everything and it ends up a subdirectory
>>>>
>>>> > 2) what are the vital lines to look for in .../test/t/logs/error_log
>>>> (or
>>>> > what is the difference between :alert and :error lines)?
>>>>
>>>> It's just a severity. Alert is more severe than error. You would only
>>>> check the error_log if you were chasing down a failed test
>>>>
>>>> (you can also ./testall -v foo/bar.t to sometimes get more info)
>>>>
>>>> --
>>>> Eric Covener
>>>> [email protected]
>>>>
>>>
>>>
>>
>
