Re: Gentoo (Was: mod_python 3.2.3b available for testing)

2005-10-27 Thread Gregory (Grisha) Trubetskoy


If we don't get an resolution on this Gentoo issue - should we just go 
ahead and release the file anyway? Hopefully then someone will fix it 
before the final release?


Grisha


On Tue, 25 Oct 2005, Gregory (Grisha) Trubetskoy wrote:



Hmmm... Looking at /usr/lib/python2.4/httplib.py, sock.readline() gets an EOF 
upon reading the first byte. Do you see anything in the error logs associated 
with this, like a segfault?


To make it easier to isolate, try editing test.py to comment out all other 
tests and just leave this one. Look for a line that looks like:


   perRequestSuite.addTest(PerRequestTestCase(test_req_headers_out))

and comment out every other test in this block but this one, then rerun it. 
At the end you should have a log file in the logs directory, hopefully it 
will contain a clue.


Thanks!

On Tue, 25 Oct 2005, Dominic Wong wrote:


-1 for Gentoo Linux 2.6.13-gentoo-r3
Apache 2.0.54
Python 2.4.1



* Testing req.headers_out
connect: (127.0.0.1, 32873)
send: 'GET / HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: 
test_req_headers_out:32873\r\n\r\n'

reply: ''
E



==
ERROR: test_req_headers_out (__main__.PerRequestTestCase)
--
Traceback (most recent call last):
File test.py, line 597, in test_req_headers_out
  response = conn.getresponse()
File /usr/lib/python2.4/httplib.py, line 863, in getresponse
  response.begin()
File /usr/lib/python2.4/httplib.py, line 333, in begin
  version, status, reason = self._read_status()
File /usr/lib/python2.4/httplib.py, line 297, in _read_status
  raise BadStatusLine(line)
BadStatusLine

--




Re: Gentoo (Was: mod_python 3.2.3b available for testing)

2005-10-27 Thread Jim Gallacher

Gregory (Grisha) Trubetskoy wrote:


If we don't get an resolution on this Gentoo issue - should we just go 
ahead and release the file anyway? Hopefully then someone will fix it 
before the final release?


Since we have not received any additional information on this I think we 
should proceed.


However there is also the issue of Too many cookies using mod_python 
3.2.2b from a thread on the mod_python list. I don't know if we should 
generate another beta or just fix it in 3.2 final. The fix is very 
simple - remove 2 lines which had been added for the get_session 
feature, but that feature didn't make it into 3.2.


There is also the issue of ./configure failing for x86-64 platforms. 
Again, it is a very simple fix - 3 lines in configure.in.


I'll create JIRA issues and commit the fixes for these real soon. 
(tonight - maybe).


To what extent can a final release differ from the last beta, Grisha? Is 
it OK to make some small changes from one to the other? When would 
changes be considered critical enough to require a new beta release round?


Regards,
Jim


Grisha


On Tue, 25 Oct 2005, Gregory (Grisha) Trubetskoy wrote:



Hmmm... Looking at /usr/lib/python2.4/httplib.py, sock.readline() gets 
an EOF upon reading the first byte. Do you see anything in the error 
logs associated with this, like a segfault?


To make it easier to isolate, try editing test.py to comment out all 
other tests and just leave this one. Look for a line that looks like:


   perRequestSuite.addTest(PerRequestTestCase(test_req_headers_out))

and comment out every other test in this block but this one, then 
rerun it. At the end you should have a log file in the logs directory, 
hopefully it will contain a clue.


Thanks!

On Tue, 25 Oct 2005, Dominic Wong wrote:


-1 for Gentoo Linux 2.6.13-gentoo-r3
Apache 2.0.54
Python 2.4.1




* Testing req.headers_out
connect: (127.0.0.1, 32873)
send: 'GET / HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: 
test_req_headers_out:32873\r\n\r\n'

reply: ''
E




==
ERROR: test_req_headers_out (__main__.PerRequestTestCase)
--
Traceback (most recent call last):
File test.py, line 597, in test_req_headers_out
  response = conn.getresponse()
File /usr/lib/python2.4/httplib.py, line 863, in getresponse
  response.begin()
File /usr/lib/python2.4/httplib.py, line 333, in begin
  version, status, reason = self._read_status()
File /usr/lib/python2.4/httplib.py, line 297, in _read_status
  raise BadStatusLine(line)
BadStatusLine

--









Re: Gentoo (Was: mod_python 3.2.3b available for testing)

2005-10-27 Thread Gregory (Grisha) Trubetskoy


I think the proper thing to do (i forgot about the cookie and x86-64 
issues) is to consider 3.2.3b as shut down by pre-release testing, so it's 
just going to be a version that will never be publicly released.


The next step is to apply the fixes you mentioned below and roll a 3.2.4b, 
then submit it to the list for test/vote for public release.


Grisha

On Thu, 27 Oct 2005, Jim Gallacher wrote:


Gregory (Grisha) Trubetskoy wrote:


If we don't get an resolution on this Gentoo issue - should we just go 
ahead and release the file anyway? Hopefully then someone will fix it 
before the final release?


Since we have not received any additional information on this I think we 
should proceed.


However there is also the issue of Too many cookies using mod_python 3.2.2b 
from a thread on the mod_python list. I don't know if we should generate 
another beta or just fix it in 3.2 final. The fix is very simple - remove 2 
lines which had been added for the get_session feature, but that feature 
didn't make it into 3.2.


There is also the issue of ./configure failing for x86-64 platforms. Again, 
it is a very simple fix - 3 lines in configure.in.


I'll create JIRA issues and commit the fixes for these real soon. (tonight - 
maybe).


To what extent can a final release differ from the last beta, Grisha? Is it 
OK to make some small changes from one to the other? When would changes be 
considered critical enough to require a new beta release round?


Regards,
Jim


Grisha


On Tue, 25 Oct 2005, Gregory (Grisha) Trubetskoy wrote:



Hmmm... Looking at /usr/lib/python2.4/httplib.py, sock.readline() gets 
an EOF upon reading the first byte. Do you see anything in the error 
logs associated with this, like a segfault?


To make it easier to isolate, try editing test.py to comment out all 
other tests and just leave this one. Look for a line that looks like:


   perRequestSuite.addTest(PerRequestTestCase(test_req_headers_out))

and comment out every other test in this block but this one, then rerun 
it. At the end you should have a log file in the logs directory, 
hopefully it will contain a clue.


Thanks!

On Tue, 25 Oct 2005, Dominic Wong wrote:


-1 for Gentoo Linux 2.6.13-gentoo-r3
Apache 2.0.54
Python 2.4.1




* Testing req.headers_out
connect: (127.0.0.1, 32873)
send: 'GET / HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: 
test_req_headers_out:32873\r\n\r\n'

reply: ''
E




==
ERROR: test_req_headers_out (__main__.PerRequestTestCase)
--
Traceback (most recent call last):
File test.py, line 597, in test_req_headers_out
  response = conn.getresponse()
File /usr/lib/python2.4/httplib.py, line 863, in getresponse
  response.begin()
File /usr/lib/python2.4/httplib.py, line 333, in begin
  version, status, reason = self._read_status()
File /usr/lib/python2.4/httplib.py, line 297, in _read_status
  raise BadStatusLine(line)
BadStatusLine

--