Tyler MacDonald <[EMAIL PROTECTED]> wrote:
> > I've seen this recently as well, but I don't think it's primarily an
> > Apache-Test issue.  at least not a code-based one - I think it happens when
> > stale A-T files are left lying around and are reused under various
> > circumstances...
>       Aha! That did it. :) Thanks!!!

        OK, so now there's an entirely new problem;

        "./Build test" starts working right away and all my tests pass, but
"./Build testcover" fails even after getting it's
APACHE_TEST_STARTUP_TIMEOUT value really, really high:

------snip------
$ APACHE_TEST_STARTUP_TIMEOUT=420 ./Build testcover
lib/Apache2/AUS.pm -> blib/lib/Apache2/AUS.pm
/usr/bin/perl -I /home/faraway/dev/Apache2-AUS/blib/lib -I
/home/faraway/dev/Apache2-AUS/blib/arch t/TEST -clean
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl /home/faraway/dev/Apache2-AUS/t/TEST
-clean
/usr/bin/perl -I /home/faraway/dev/Apache2-AUS/blib/lib -I
/home/faraway/dev/Apache2-AUS/blib/arch t/TEST -bugreport -verbose=0
[warning] setting ulimit to allow core files
ulimit -c unlimited; /usr/bin/perl /home/faraway/dev/Apache2-AUS/t/TEST
-bugreport -verbose=0
/usr/sbin/apache2  -d /home/faraway/dev/Apache2-AUS/t -f
/home/faraway/dev/Apache2-AUS/t/conf/httpd.conf -D APACHE2 -D
PERL_USEITHREADS
using Apache/2.0.55 (prefork MPM)

waiting 420 seconds for server to start:
....................................................................................................................................................................................................................................................................................................................................................................................................................................
waiting 420 seconds for server to start: not ok
[  error] giving up after 421 secs. If you think that your system
is slow or overloaded try again with a longer timeout value.
by setting the environment variable APACHE_TEST_STARTUP_TIMEOUT
to a high value (e.g. 720) and repeat the last command.

[  error] server failed to start! (please examine t/logs/error_log)
cover
Reading database from /home/faraway/dev/Apache2-AUS/cover_db
Use of uninitialized value in string ne at
/usr/local/lib/perl/5.8.8/Devel/Cover/DB.pm line 174.
Use of uninitialized value in string ne at
/usr/local/lib/perl/5.8.8/Devel/Cover/DB.pm line 174.


---------------------------- ------ ------ ------ ------ ------ ------
------
File                           stmt   bran   cond    sub    pod   time
total
---------------------------- ------ ------ ------ ------ ------ ------
------
lib/Apache2/AUS.pm             42.9    0.0    0.0   75.0  100.0   42.9
38.3
...Apache2/AUS/RequestRec.pm   50.0    0.0    0.0   66.7    0.0   11.2
34.8
lib/Apache2/AUS/Util.pm        53.2    0.0    0.0   63.6    0.0   45.9
44.8
Total                          48.1    0.0    0.0   68.2   23.1  100.0
40.5
---------------------------- ------ ------ ------ ------ ------ ------
------


Writing HTML output to /home/faraway/dev/Apache2-AUS/cover_db/coverage.html
...
done.
[EMAIL PROTECTED]:~/dev/Apache2-AUS$ cat t/logs/error_log
Devel::Cover: Can't open -e for MD5 digest: No such file or directory
------snip------


        I'm going to dig into this more when I get home... Any ideas??

        Thanks,
                Tyler


Reply via email to