Dmitry Karasik wrote:
I found the change that triggers the bug with mod_perl tests:
This line
Apache::TestRequest::user_agent( keep_alive => 1);
added in stdin.t does it. I hope it is convincing enough now. I still don't
understand why it was so hard to try to reproduce my test setup with netcat.
Does this test pass for you when you apply the patch in this thread?
http://marc.info/?l=apache-modperl&m=119072925228529&w=2
/dk
My log:
$ ./t/TEST -start-httpd -one-process
/usr/local/sbin/httpd -D ONE_PROCESS -d /usr/ports/www/mod_perl2/work/mod_perl-2.0.3/ModPerl-Registry/t -f /usr/ports/www/mod_perl2/work/mod_perl-2.0.3/ModPerl-Registry/t/conf/httpd.conf -D APACHE2
using Apache/2.2.6 (prefork MPM)
waiting 90 seconds for server to start: ...
waiting 90 seconds for server to start: ok (waited 2 secs)
server localhost:8529 started
$ t/TEST -run-tests -verbose t/stdin.t
t/stdin....1..2
# Running under perl version 5.008008 for freebsd
# Current time local: Mon Oct 8 11:05:12 2007
# Current time GMT: Mon Oct 8 09:05:12 2007
# Using Test.pm version 1.25
# Using Apache/Test.pm version 1.29
# testing : form submission ok under mod_perl
# expected: (?-xism:submitted)
# received: submitted / mod_perl/2.0.3
ok 1
# testing : stdin reset, form submission ok under cgi
# expected: (?-xism:submitted)
# received:
not ok 2
# Failed test 2 in t/stdin.t at line 25
FAILED test 2
Failed 1/2 tests, 50.00% okay
Failed Test Stat Wstat Total Fail List of Failed
-------------------------------------------------------------------------------
t/stdin.t 2 1 2
Failed 1/1 test scripts. 1/2 subtests failed.
Files=1, Tests=2, 2 wallclock secs ( 0.30 cusr + 0.05 csys = 0.36 CPU)
Failed 1/1 test programs. 1/2 subtests failed.
[ error] error running tests (please examine t/logs/error_log)
[1] 86918 exit 1 t/TEST -run-tests -verbose t/stdin.t
On Tue, Oct 02, 2007 at 08:16:20PM +0200, Torsten Foertsch wrote:
On Tuesday 02 October 2007 08:54, Dmitry Karasik wrote:
Can you try the updated test patch that Torsten replied to the list with:
http://marc.info/?l=apache-modperl&m=119074979901161&w=2
The test succeeds in boths cases, on both patched and unpatched mod_perl.
I don't know why is that, but I think that shouldn't be a reason to ignore
the error that is reproduced using the test case I proposed (and
of course because of the Pesticide Paradox :)
Try the following (assuming you are using prefork):
0) cd ModPerl-Registry/
1) start the testsuite with t/TEST -start-httpd
2) kill all apache children (workers). The supervisor apache should respawn
new children.
3) Then run your test: t/TEST -run-tests -verbose t/stdin.t
I hope it fails this way. If yes then maybe a way to construct a proper test
is to add a new vhost with very limited MaxRequestsPerChild (1 or 2)
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
