stas 2003/05/26 16:17:43 Modified: src/docs/2.0/user/help help.pod Log: add a section on 'make test failures' Revision Changes Path 1.19 +36 -1 modperl-docs/src/docs/2.0/user/help/help.pod Index: help.pod =================================================================== RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/help/help.pod,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- help.pod 18 Feb 2003 03:38:46 -0000 1.18 +++ help.pod 26 May 2003 23:17:43 -0000 1.19 @@ -70,7 +70,7 @@ The C<t/REPORT> utility is autogenerated when C<perl Makefile.PL> is run, so you should have it already after building mod_perl. -META: soon we will have C<modperlbug> report script which will be +META: soon we will have C<mp2bug> report script which will be installed system-wide. For now, if you don't have the source, you can create the report by running the following: @@ -95,6 +95,41 @@ Finally don't forget to copy-n-paste (not type!) the B<relevant> part of the I<error_log> file (not the whole file!). + +=head2 'C<make test>' Failures + +If when running 'make test' some of the tests fail, please re-run them +in the verbose mode and post the output of the run and the contents of +the I<error_log> file to the list. + +For example if 'C<make test>' reports: + + Failed Test Stat Wstat Total Fail Failed List of Failed + ------------------------------------------------------------------ + compat/apache_util.t 15 1 6.67% 13 + modperl/pnotes.t 5 1 20% 2 + +Do the following: + + % cd modperl-1.99_xx + % make test TEST_VERBOSE=1 \ + TEST_FILES="compat/apache_util.t modperl/pnotes.t" + +or use an altenative way: + + % cd modperl-1.99_xx + % rm t/log/error_log + % t/TEST -v compat/apache_util.t modperl/pnotes.t + +If you are using the latter, remember to remove the I<error_log> file +before running tests, so you won't have clutter from the previous +run. C<make test> always removes the old I<error_log> file for you. + +Also please notice that there is more than one C<make test> run. The +first one is running at the top directory, the second inside a +sub-directory I<ModPerl-Registry/>, so if you get failures in the +second run, make sure to chdir() to that directory before you look at +the I<error_log> file and re-run tests in the verbose mode. =head2 Resolving Segmentation Faults
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
