So, back to testing again - on the same system where 2.4.10-distro passed
all tests it ran, 2.2.28-dev has a few errors reporting - and I need to
figure out why mod_proxy is not being built (or maybe it is only that it is
not Loaded)

Summary:
cc is a tracked alias for /usr/vac/bin/cc
root@x099:[/data/prj/apache/httpd/test]oslevel -s
7100-02-04-1341
root@x099:[/data/prj/apache/httpd/test]type perl
perl is /usr/bin/perl
root@x099:[/data/prj/apache/httpd/test]ls -l /usr/bin/perl
lrwxrwxrwx    1 root     system           29 Aug 05 21:00 /usr/bin/perl ->
/usr/opt/perl5/bin/perl5.10.1

root@x099:[/data/prj/apache/httpd/test]find /opt/httpd -name apxs
/opt/httpd/sbin/apxs
root@x099:[/data/prj/apache/httpd/test]perl Makefile.PL -apxs
/opt/httpd/sbin/apxs
[   info] generating script ./Apache-Test.save/t/cgi-bin/
next_available_port.pl
[   info] generating script ./Apache-Test.save/t/cgi-bin/cookies.pl
...
Checking for File::Spec...ok
Checking for Cwd...ok
Generating a Unix-style Makefile
Writing Makefile for httpd-test
Writing MYMETA.yml and MYMETA.json
root@x099:[/data/prj/apache/httpd/test]

root@x099:[/data/prj/apache/httpd/test]find . ! -user michael -exec chown
michael {} \;
root@x099:[/data/prj/apache/httpd/test]su michael
root@x099:[/data/prj/apache/httpd/test]t/TEST
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/opt/perl5/bin/perl
/data/prj/apache/httpd/test/t/TEST
cd test_rwrite && make .libs/mod_test_rwrite.so
make[1]: Entering directory
`/data/prj/apache/httpd/test/c-modules/test_rwrite'
/opt/httpd/sbin/apxs -D APACHE2  -I/data/prj/apache/httpd/test/c-modules
-c mod_test_rwrite.c
...
using Apache/2.2.28-dev (worker MPM)

waiting 60 seconds for server to start: ...
waiting 60 seconds for server to start: ok (waited 2 secs)
server loopback:8529 started
server loopback:8530 listening (mod_nntp_like)
server loopback:8531 listening (mod_nntp_like_ssl)
server loopback:8532 listening (mod_ssl)
server loopback:8533 listening (ssl_optional_cc)
server loopback:8534 listening (ssl_pr33791)
server loopback:8535 listening (proxy_http_bal1)
server loopback:8536 listening (proxy_http_bal2)
server loopback:8537 listening (proxy_http_balancer)
server loopback:8538 listening (cve_2011_3368_rewrite)
server loopback:8539 listening (proxy_http_reverse)
server loopback:8540 listening (cve_2011_3368)
server loopback:8541 listening (mod_headers)
server loopback:8542 listening (error_document)
server loopback:8543 listening (http_strict)
server loopback:8544 listening (mod_vhost_alias)
server loopback:8545 listening (mod_include)
server loopback:8546 listening (proxy_http_https)
server loopback:8547 listening (proxy_https_https)
server loopback:8548 listening (proxy_https_http)
[   info] adding source lib /data/prj/apache/httpd/test/Apache-Test/lib to
@INC
t/apache/404.t ...................... ok
t/apache/acceptpathinfo.t ........... ok
...
t/ssl/env.t ......................... ok
t/ssl/extlookup.t ................... 1/4 # Failed test 2 in
t/ssl/extlookup.t at line 27
t/ssl/extlookup.t ................... Failed 1/4 subtests
t/ssl/fakeauth.t .................... ok
t/ssl/headers.t ..................... ok
t/ssl/http.t ........................ ok
t/ssl/pr12355.t ..................... ok
t/ssl/pr43738.t ..................... ok
t/ssl/proxy.t ....................... skipped: cannot find module
'mod_proxy', cannot find module 'proxy_http.c'
t/ssl/require.t ..................... 2/10 # Failed test 9 in
t/ssl/require.t at line 44
t/ssl/require.t ..................... Failed 1/10 subtests
t/ssl/v2.t .......................... ok
t/ssl/varlookup.t ................... ok
t/ssl/verify.t ...................... ok

Test Summary Report
-------------------
t/ssl/extlookup.t                 (Wstat: 0 Tests: 4 Failed: 1)
  Failed test:  2
t/ssl/require.t                   (Wstat: 0 Tests: 10 Failed: 1)
  Failed test:  9
Files=109, Tests=3503, 533 wallclock secs ( 4.66 usr  0.47 sys + 161.53
cusr 73.62 csys = 240.28 CPU)
Result: FAIL
Failed 2/109 test programs. 2/3503 subtests failed.
[warning] server loopback:8529 shutdown
[warning] port 8529 still in use...
......done
[  error] error running tests (please examine t/logs/error_log)



On Thu, Aug 7, 2014 at 6:05 PM, Michael Felt <mamf...@gmail.com> wrote:

> Actually, there are more files involved - if you read the CHANGES you
> might understand. So, here is a tar file with everything.
>
> As a zip file, because my mailer refuses the .tar file
>
>
>
> On Thu, Aug 7, 2014 at 5:43 PM, Michael Felt <mamf...@gmail.com> wrote:
>
>> Made updates to the wiki - and, although probably too late for 2.2.28
>> release - please review this patch for build/aix stuff. Who knows, if/when
>> a 2.2.29 release ever comes these will be there too.
>>
>> p.s. starting test run for trunk (aka 2.2.28)
>>
>> p.p.s. The idea is that the CHANGES file be added in build/aix. If that
>> is a sin of some sort, please just append to build/aix/README.aix I will
>> see what it becomes when trunk is updated.
>>
>>
>> On Thu, Aug 7, 2014 at 9:08 AM, Michael Felt <mamf...@gmail.com> wrote:
>>
>>> I already have a login. I have a problem with writing in wiki's - never
>>> satisfied with how I put it there, but I shall add/update the info I know.
>>>
>>>
>>> On Wed, Aug 6, 2014 at 2:40 PM, Eric Covener <cove...@gmail.com> wrote:
>>>
>>>> On Wed, Aug 6, 2014 at 8:37 AM, Michael Felt <mamf...@gmail.com> wrote:
>>>> > The good news:
>>>> > All tests successful.
>>>> > Files=109, Tests=4763, 645 wallclock secs ( 5.69 usr  0.51 sys +
>>>> 175.37 cusr
>>>> > 113.07 csys = 294.64 CPU)
>>>> > Result: PASS
>>>> >
>>>> > How: tested on AIX 7.1 with a more modern perl version. There is one
>>>> > sub-module (Test::Try if i recall correctly)  - that demands perl
>>>> 5.10 as a
>>>> > minimum. So without that there are probably several perl modules that
>>>> are
>>>> > not sufficient for the tests to be processed correctly)
>>>> >
>>>> > For now I am just going to be happy with: All tests successful. ...
>>>> Result:
>>>> > PASS
>>>> >
>>>>
>>>> Can you take a pass through https://wiki.apache.org/httpd/AIXPlatform
>>>> while it's still fresh? You may have to register a nickname there and
>>>> then ask for write access (spam problems
>>>>
>>>
>>>
>>
>

Reply via email to