Re: mod_python 3.3.0-dev-20060321 available for testing
On 3/22/06, Graham Dumpleton [EMAIL PROTECTED] wrote: That is the error I was getting from ab in Apache 2.2. Change test.py to explicitly use ab from Apache 2.0 and see if they go away. Here is the previous information I posted about core_input_filter errors caused by ab test tool in Apache 2.2. http://www.mail-archive.com/python-dev@httpd.apache.org/msg01535.html I believe that this is the APR kqueue bug on Mac OS X. (ab uses the pollset API.) This should be worked around with the just-released APR 1.2.6 - which will be included in the forthcoming httpd 2.2.1. I will note that if you see odd stuff like this with httpd or APR, please don't hesitate to post to [EMAIL PROTECTED] or to [EMAIL PROTECTED] Your issue would have been identified way earlier if you had posted there. =) -- justin
Re: mod_python 3.3.0-dev-20060321 available for testing
+1 Linux Debian Sid, apache 2.0.55 mpm-prefork, python 2.3.5
+1 Linux Debian Sid, apache 2.2.0 mpm-prefork, python 2.4.2
New Importer:
+1 Linux Debian Sid, apache 2.0.55 mpm-prefork, python 2.3.5
+1 Linux Debian Sid, apache 2.2.0 mpm-prefork, python 2.4.2
Jim Gallacher wrote:
mod_python-3.3.0-dev-20060321 is available for testing.
We are asking the mod_python development community for assistance in
testing the current development branch. Hopefully this will allow us to
catch new bugs or regressions early, and when we are ready for the next
release the beta cycle will be much shorter.
This snapshot addresses 33 issues since 3.2.7 was released, including
apache 2.2 support and the introduction of a new module importer.
The files are (temporarily) available here:
http://people.apache.org/~jgallacher/mod_python/dist/
Please download it, then do the usual
$ ./configure --with-apxs=/wherever/it/is
$ make
$ (su)
# make install
Then (as non-root user!)
$ make check
or if you prefer to run the tests the old way:
$ cd test
$ python test.py
Make a note of any failing tests.
If all the tests pass, give the new module importer a workout by
uncommenting line 328 in test/test.py:
#PythonOption('mod_python.future.importer *'),
and then re-run the tests.
$ make check
And see if any tests fail. If they pass, send a +1 to the list, if they
fail, send the details (the versions of OS, Python and Apache, the test
output, and suggestions, if any).
Thank you for your assistance,
Jim Gallacher
Re: mod_python 3.3.0-dev-20060321 available for testing
Nicolas, could you make a Win32 binary for us poor people? -- Mike Looijmans Philips Natlab / Topic Automation
Re: mod_python 3.3.0-dev-20060321 available for testing
-1 Slackware 10.1, Apache 2.2.0 (mpm-prefork), Python 2.4
My applications are working, but make check produces these errors:
==
FAIL: test_req_auth_type (__main__.PerRequestTestCase)
--
Traceback (most recent call last):
File test.py, line 673, in test_req_auth_type
self.fail(`rsp`)
AssertionError: '!DOCTYPE HTML PUBLIC -//IETF//DTD HTML
2.0//EN\nhtmlhead\ntitle500 Internal Server
Error/title\n/headbody\nh1Internal Server Error/h1\npThe
server encountered an internal error or\nmisconfiguration and was unable
to complete\nyour request./p\npPlease contact the server
administrator,\n [no address given] and inform them of the time the
error occurred,\nand anything you might have done that may have\ncaused
the error./p\npMore information about this error may be
available\nin the server error log./p\n/body/html\n'
--
Ran 60 tests in 231.452s
FAILED (failures=1)
F Stopping Apache...
/usr/local/apache2/bin/httpd -k stop -f
/home/jorey/src/mod_python-3.3.0-dev-20060321/test/conf/test.conf
==
FAIL: testPerRequestTests (__main__.PerInstanceTestCase)
--
Traceback (most recent call last):
File test.py, line 2467, in testPerRequestTests
self.failUnless(result.wasSuccessful())
AssertionError
--
Jim Gallacher wrote:
mod_python-3.3.0-dev-20060321 is available for testing.
We are asking the mod_python development community for assistance in
testing the current development branch. Hopefully this will allow us to
catch new bugs or regressions early, and when we are ready for the next
release the beta cycle will be much shorter.
This snapshot addresses 33 issues since 3.2.7 was released, including
apache 2.2 support and the introduction of a new module importer.
The files are (temporarily) available here:
http://people.apache.org/~jgallacher/mod_python/dist/
Please download it, then do the usual
$ ./configure --with-apxs=/wherever/it/is
$ make
$ (su)
# make install
Then (as non-root user!)
$ make check
or if you prefer to run the tests the old way:
$ cd test
$ python test.py
Make a note of any failing tests.
If all the tests pass, give the new module importer a workout by
uncommenting line 328 in test/test.py:
#PythonOption('mod_python.future.importer *'),
and then re-run the tests.
$ make check
And see if any tests fail. If they pass, send a +1 to the list, if they
fail, send the details (the versions of OS, Python and Apache, the test
output, and suggestions, if any).
Thank you for your assistance,
Jim Gallacher
Re: mod_python 3.3.0-dev-20060321 available for testing
Nicolas Lehuen wrote .. 2006/3/22, Nicolas Lehuen [EMAIL PROTECTED]: However I have a -1 on Python 2.2 with a LOT of test failures, but I guess we won't support Python 2.2 for mod_python 3.3 ? Sorry, my -1 was due to a configuration problem, everything works on Python 2.2. +1 for mod_python 3.3.0-dev-20060321 on Windows 2000 SP4 + ActivePython 2.2.3 + Apache 2.0.55 If you run the tests with the new importer, I would not have expected it to get very far with Python 2.2. This is because at one point it does: sys.meta_path.insert(0, _ModuleImporter()) Our understanding so far had been that sys.meta_path would only have appeared in Python 2.3, thus the import should have failed when that attribute was used. Graham
Re: mod_python 3.3.0-dev-20060321 available for testing
Graham Dumpleton wrote .. On 23/03/2006, at 5:06 AM, Jim Gallacher wrote: That's another reason to rewrite the unit tests. It's too hard to sort out the wheat from the chaff. I don't think this is related to your failing test, but I noticed the following, repeated numerous times throughout your log: [Wed Mar 22 09:09:30 2006] [info] [client 127.0.0.1] (32)Broken pipe: core_output_filter: writing data to the network I think we need to investigate this one. That is the error I was getting from ab in Apache 2.2. Change test.py to explicitly use ab from Apache 2.0 and see if they go away. Here is the previous information I posted about core_input_filter errors caused by ab test tool in Apache 2.2. http://www.mail-archive.com/python-dev@httpd.apache.org/msg01535.html I only had it occur once for each test run and specifically the global lock test, since that is the only place ab is used. Thus cause may be different this time. Graham
Re: mod_python 3.3.0-dev-20060321 available for testing
2006/3/22, Graham Dumpleton [EMAIL PROTECTED]: Nicolas Lehuen wrote .. 2006/3/22, Nicolas Lehuen [EMAIL PROTECTED]: However I have a -1 on Python 2.2 with a LOT of test failures, but I guess we won't support Python 2.2 for mod_python 3.3 ? Sorry, my -1 was due to a configuration problem, everything works on Python 2.2. +1 for mod_python 3.3.0-dev-20060321 on Windows 2000 SP4 + ActivePython 2.2.3 + Apache 2.0.55 If you run the tests with the new importer, I would not have expected it to get very far with Python 2.2. This is because at one point it does: sys.meta_path.insert(0, _ModuleImporter()) Our understanding so far had been that sys.meta_path would only have appeared in Python 2.3, thus the import should have failed when that attribute was used. Graham Duh, I have forgotten to run the test using the new importer. All three results were therefore using the old importer. Regards, Nicolas
Re: mod_python 3.3.0-dev-20060321 available for testing
I've tested with and without the new importer on Windows XP SP2 +
Python 2.4.2 + Apache 2.2.0 and everything works except the
test_req_auth_type test, which signals a 500 error. This is what the
error_log contains about this test :
[Wed Mar 22 07:16:03 2006] [warn] mod_python
(pid=5140,interpreter='test_req_auth_type'): Module directory listed
in sys.path. This may cause problems. Please check code. Code file
being imported is C:\\projets\\mod_python\\test\\htdocs\\tests.py.
[Wed Mar 22 07:16:03 2006] [notice] mod_python
(pid=5140,interpreter='test_req_auth_type'): Importing module
'C:\\projets\\mod_python\\test\\htdocs\\tests.py'
[Wed Mar 22 07:16:03 2006] [crit] [client 127.0.0.1] configuration
error: couldn't check access. No groups file?: /tests.py
[Wed Mar 22 07:16:03 2006] [error] [client 127.0.0.1] No Authn
provider configured
The piece of code that emits the No groups file? seem to reside in
libhttpd.dll, a part of Apache 2.2, so I guess it's a problem with my
Apache setup. I'll try this on my Apache 2.0 setup on my PC at work
and let you know.
Regards,
Nicolas
2006/3/22, Jim Gallacher [EMAIL PROTECTED]:
mod_python-3.3.0-dev-20060321 is available for testing.
We are asking the mod_python development community for assistance in
testing the current development branch. Hopefully this will allow us to
catch new bugs or regressions early, and when we are ready for the next
release the beta cycle will be much shorter.
This snapshot addresses 33 issues since 3.2.7 was released, including
apache 2.2 support and the introduction of a new module importer.
The files are (temporarily) available here:
http://people.apache.org/~jgallacher/mod_python/dist/
Please download it, then do the usual
$ ./configure --with-apxs=/wherever/it/is
$ make
$ (su)
# make install
Then (as non-root user!)
$ make check
or if you prefer to run the tests the old way:
$ cd test
$ python test.py
Make a note of any failing tests.
If all the tests pass, give the new module importer a workout by
uncommenting line 328 in test/test.py:
#PythonOption('mod_python.future.importer *'),
and then re-run the tests.
$ make check
And see if any tests fail. If they pass, send a +1 to the list, if they
fail, send the details (the versions of OS, Python and Apache, the test
output, and suggestions, if any).
Thank you for your assistance,
Jim Gallacher
