Still seeing a failure - seems to be the same thing I saw back on 3.2.5b

and suspiciously similar to this report on Mac OSX

FreeBSD 6.0
Apache 2.0.55 (prefork) port built WITH_THREADS=1
Python 2.4.2 built from ports with these port options

ERROR: test_connectionhandler (__main__.PerRequestTestCase)
Traceback (most recent call last):
  File "", line 1336, in test_connectionhandler
    f = urllib.urlopen(url)
  File "/usr/local/lib/python2.4/", line 77, in urlopen
  File "/usr/local/lib/python2.4/", line 185, in open
    return getattr(self, name)(url)
  File "/usr/local/lib/python2.4/", line 317, in open_http
    return self.http_error(url, fp, errcode, errmsg, headers)
  File "/usr/local/lib/python2.4/", line 334, in http_error
    return self.http_error_default(url, fp, errcode, errmsg, headers)
File "/usr/local/lib/python2.4/", line 574, in http_error_default
    return addinfourl(fp, headers, "http:" + url)
  File "/usr/local/lib/python2.4/", line 863, in __init__
    addbase.__init__(self, fp)
  File "/usr/local/lib/python2.4/", line 813, in __init__ =
AttributeError: 'NoneType' object has no attribute 'read'

Ran 45 tests in 65.420s

FAILED (errors=1)
F  Stopping Apache...
/usr/local/sbin/httpd -k stop -f /home/barryp/mod_python-3.2.6/test/conf/test.conf

FAIL: testPerRequestTests (__main__.PerInstanceTestCase)
Traceback (most recent call last):
  File "", line 1928, in testPerRequestTests

Ran 6 tests in 121.462s

FAILED (failures=1)

GDB backtrace
#0  0x00000058 in ?? ()
#1 0x2849b4f5 in _conn_read () from /home/barryp/mod_python-3.2.6/src/ #2 0x2849b6c9 in conn_readline () from /home/barryp/mod_python-3.2.6/src/ #3 0x284e4ef2 in PyEval_EvalFrame () from /home/barryp/mod_python-3.2.6/src/ #4 0x284e5091 in PyEval_EvalFrame () from /home/barryp/mod_python-3.2.6/src/ #5 0x284e56e4 in PyEval_EvalCodeEx () from /home/barryp/mod_python-3.2.6/src/ #6 0x2851ede2 in function_call () from /home/barryp/mod_python-3.2.6/src/ #7 0x284a5f44 in PyObject_Call () from /home/barryp/mod_python-3.2.6/src/ #8 0x284ab986 in instancemethod_call () from /home/barryp/mod_python-3.2.6/src/ #9 0x284a5f44 in PyObject_Call () from /home/barryp/mod_python-3.2.6/src/ #10 0x284a6119 in PyObject_CallMethod () from /home/barryp/mod_python-3.2.6/src/ #11 0x284a35bf in PythonConnectionHandler () from /home/barryp/mod_python-3.2.6/src/
#12 0x0807025a in ap_run_process_connection ()
#13 0x08066285 in child_main ()
#14 0x080664af in make_child ()
#15 0x08066540 in startup_children ()
#16 0x08066bc3 in ap_mpm_run ()
#17 0x0806be77 in main ()

I'm suspicious about whether the problem is actually in the connection handler code - if I strip the down to just run test_connectionhandler, it works fine. But after some trial and error adding things back, it seems the simplest test combination that causes the problem is to run test_fileupload, and then test_connectionhandler.

So I'm basically just running

[EMAIL PROTECTED]:~/mod_python-3.2.6/test>python

* Running the per-request test suite...
  Creating config....
    listen port: 57772
  Starting Apache....
/usr/local/sbin/httpd -k start -f /home/barryp/mod_python-3.2.6/test/conf/test.conf

  * Testing 1 MB file upload support
    --> Send + process + receive took 0.577 s
  * Testing PythonConnectionHandler
  * Testing internally (status messages go to error_log)

So I wonder if some non-connection-handling code is stomping over some structure that doesn't happen to be used til the connection-handler is exercised? In that case it maybe we can't just shrug it off figuring it's "...hardly likely that anyone would use connection handlers with mod_python for anything meaningful."


Reply via email to