Hi David, One thing I don't understand is why you have "foreign" PythonOption definitions in your test setup. Are you sure you have re-created a clean testconf.py file from testconf.py.in ? I've write a little bit of documentation in test/README, please try to follow it.
It seems to me that the test failures all come from this strange test configuration. It looks like mod_python is interfering with some already existing filters, like MultiView. Note that there is a bug under Win32 which I should have reported way before... In some situation, when an exception is raised in mod_python during normal operation, Apache will segfault the next time is is stopped or restarted. It only occurs with a specific exception is raised, maybe when a handler module fails to load. The reason why I haven't reported it yet is that it only occured on my development computer, not my production servers, so I thought it was something caused by my setup. Apparently you have the same problem, hence the segfault when the Apache server is stopped. I'll have to investigate this problem more thoroughly. So please try to re-run the test in a clean slate environment. It'd be interesting to see why and how your current configuration "contaminates" the test configuration, though. Regards, Nicolas 2006/2/8, David Fraser <[EMAIL PROTECTED]>: > Jim Gallacher wrote: > > Gregory (Grisha) Trubetskoy wrote: > >> > >> I think we have enough +1's. (If someone could tally them up in a > >> single e-mail, that'd be great.) Should we start a core-group vote, > >> or wait some more? On the bash issue - I think we can leave it as is, > >> the affected distros will just have to maintain a patch in their > >> build systems. > > > > Let's vote. > > > > Here is the test summary: > > > > +1 Debian (sid), Apache 2.0.55-prefork, Python 2.3.5 > > +1 Debian (sarge), Apache 2.0.54-worker, Python 2.3.5 > > +1 Debian (sarge), Apache 2.0.54-prefork, Python 2.3.5 > > +1 Debian (testing, aka, etch), Apache 2.0.55-worker, Python 2.3.5 > > +1 Fedora Core 4, Linux 2.6.15, Apache 2.0.54, Python 2.4.1 > > +1 FreeBSD 4.9 , Apache 2.0.50 (prefork), Python 2.3.4 > > +1 FreeBSD 4.9 , Apache 2.0.55 (prefork), Python 2.4.2 > > +1 MacOSX 10.4.4 PPC, Apache-2.0.55-prefork, Python-2.4.2 > > +1 Slackware 10.1, Apache 2.0.55 (mpm-prefork), Python 2.4 > > +1 Solaris 10 Sparc, Apache-2.0.55-prefork, Python-2.4.2 > > +1 Ubuntu 5.10 Breezy (amd64), Apache 2.0.54-worker, Python 2.4.2 > > +1 Windows 2000 SP4, Apache/2.0.55 + Python/2.2.3 > > +1 Windows 2000 SP4, Apache/2.0.55 + ActivePython/2.3.5 > > +1 Windows XP SP2, Apache/2.0.55 + ActivePython/2.4.2 > > > > With configure fixed manually to deal with bash bug: > > +1 Gentoo 2005.1 (amd64), Apache 2.0.55-prefork, Python 2.4.2 > > > > Plus we have the following tests from the svn revision which > > corresponds to 3.2.7: > > +1 trunk rev 374709 FreeBSD 6.0 Apache 2.0.55-prefork, Python 2.4.2 > I know its already been decided, but I thought I'd add another test for > Windows (seeing as Nicolas is the only one who has tested so far...) > This was with the installers Nicolas built, running the tests out of svn > version 375881 > +1 Windows XP SP2, Apache/2.0.54, Python 2.4.1 > > Unfortunately I got a failure too: > -1 Windows 2000 SP4, Apache/2.0.49, Python 2.3.3 > This even incorporated Apache segfaults ... when trying to stop with > server.register_cleanup and apache.register_cleanup > > > Other failures: > req.add_handler() when handler list is empty > PythonOption override, remove and remove2 > PythonOutputFilter > test_internal > > In all, I got 6 failures on the first 45 tests and 3 on the last 6. > > The PythonOption test failures look like they're conflicting with some > PythonOptions in my default Apache config (since the assertion errors > include things like jToolkit and jLogbook), so this seems to be an error > in the test setup that its not independent of that. > The PythonOutputFilter test also seems to be a test error, as it is > returning the *contents* of test.py in uppercase instead of TEST OK in > uppercase... > Similarly test_accesshandler_add_handler_to_empty_hl is returning the > contents of test.py > > > I wonder if the segfaults on cleanup relate to my Apache version, if so > I can try upgrading. > > Am I doing something wrong in the testing? Logs attached (zipped as the > inclusion of test.py a few times make them quite big)... > > David > > >
