stas 2004/02/09 11:15:26
Modified: todo release tests
Log:
TestDirective::perlloadmodule6 need to be loaded first is a tests todo
(not a showstopper). PerlSwitches must come before perl is started, not
much we can do about it
Revision Changes Path
1.13 +0 -24 modperl-2.0/todo/release
Index: release
===================================================================
RCS file: /home/cvs/modperl-2.0/todo/release,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -u -r1.12 -r1.13
--- release 9 Feb 2004 19:08:35 -0000 1.12
+++ release 9 Feb 2004 19:15:26 -0000 1.13
@@ -45,30 +45,6 @@
the whole thread is here:
http://marc.theaimsgroup.com/?t=103713532800003&r=1&w=2
-
-* we still have a problem with mod_perl starting from a
- vhost. consider the following config:
-
- PerlSwitches -I/foo/bar
- <VirtualHost TestDirective::perlloadmodule6>
- PerlLoadModule TestDirective::perlloadmodule6
- ...
- </VirtualHost>
-
- The value set by PerlSwitches in the main server is ignored, because
- it's not seen by mod_perl starting from vhost.
-
- overall, currently the early startup in vhost is a bunch of ugly
- workaround, which I've added everytime I came up with a config that
- wasn't working. Need to come up with a better design decisions.
-
- once this is fixed. I want the perlloadmodule6 to be loaded before
- all other perlloadmodule configs, because it tests an important
- segfault when perlloadmodule happens to start mod_perl from within a
- vhost. but because PerlSwitches from other tests are ignored, it
- can't trigger the mod_perl startup in the test suite.
-
-
- anonymous handler (for push_handlers, add_input_filter, etc), see
modperl_mgv.c: modperl_mgv_name_from_sv
1.2 +9 -0 modperl-2.0/todo/tests
Index: tests
===================================================================
RCS file: /home/cvs/modperl-2.0/todo/tests,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -u -r1.1 -r1.2
--- tests 9 Feb 2004 19:12:49 -0000 1.1
+++ tests 9 Feb 2004 19:15:26 -0000 1.2
@@ -14,3 +14,12 @@
should definitely be moved out from the main suite, as they cause
the biggest overhead (due to perl_clone).
+- TestDirective::perlloadmodule6 should be the first perlloadmodule
+ test to run, so we can test how mod_perl starts from vhost (there
+ was a segfault before). But since other tests define PerlSwitches
+ TestDirective::perlloadmodule6 must be configured afer them. so if
+ we introduce new tests suites, this test needs to be moved there
+ (may be its own test suite or co-existing with other tests which
+ don't use PerlSwitches and trigger early server startup.
+
+
