Do you mind using the build/bug_report.pl when reporting problems?
I'll consider it; do they get sent to this list where they can be discussed, or into some black-hole system where any/all exchanges are out-of-band?
currently it's not getting sent anywhere, you send it by yourself. It's just a short script that dumps all the build/os info that we might need to reproduce the problem.
It does not appear to fix it -- probably because I didn't give enough info and you were addressing the 'waiting for server to start' area rather than the one that's actually failing above.. :-(
exit 1 indicates failure, isn't it?
Any non-zero value is failure.
I've traced the logic and it seems to be correct:
Apache::TestServer::wait_till_is_up returns 0 Apache::TestServer::start returns 0 Apache::TestRun::run exits 1
You appear to be tracing the wrong path, since my run exited with 0. Note that this is NOT the first 'is it up' test, which has already succeeded, but one that happens after the verification of the listeners. Look at the excerpt again..
I think I was looking at the right pass. Can you please put this code at the beginning of TestRun.pm:
use subs qw(exit);
use Carp;
sub exit { Carp::cluck("exiting"); CORE::exit(@_) }and run again? This should print the trace and show where the exit was called from.
Thanks! _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
