You are viewing a plain text version of this content. The canonical link for it is here.
Posted to test-dev@httpd.apache.org by Rodent of Unusual Size <Ke...@Golux.Com> on 2004/04/15 05:46:41 UTC

[STATUS] (perl-framework) Wed Apr 14 23:46:41 EDT 2004

httpd-test/perl-framework STATUS:				-*-text-*-
Last modified at [$Date: 2002/03/09 05:22:48 $]

Stuff to do:
    * finish the t/TEST exit code issue (ORed with 0x2C if
      framework failed)

    * change existing tests that frob the DocumentRoot (e.g.,
      t/modules/access.t) to *not* do that; instead, have
      Makefile.PL prepare appropriate subdirectory configs
      for them.  Why?  So t/TEST can be used to test a
      remote server.

    * problems with -d perl mode, doesn't work as documented
      Message-ID: <3B...@stason.org>
      Date: Sat, 20 Oct 2001 12:58:33 +0800
      Subject: Re: perldb

Tests to be written:

    * t/apache
      - simulations of network failures (incomplete POST bodies,
        chunked and unchunked; missing POST bodies; slooow
        client connexions, such as taking 1 minute to send
        1KiB; ...)

    * t/modules/autoindex
      - something seems possibly broken with inheritance on 2.0

    * t/ssl
      - SSLPassPhraseDialog exec:
      - SSLRandomSeed exec:

Re: httpd test (perl-framework)

Posted by Stas Bekman <st...@stason.org>.
Abhishek Khandelwal wrote:
> I am getting the following error when I run the perl-test framework.
> I get this error when I run the test twice, one after another.

Abhishek, why did you CC the Test::Harness bug list? it's totally unrelated. 
Please post bug reports to that list only when you see a bug in Test::Harness, 
which it is not. Thanks.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Re: httpd test (perl-framework)

Posted by Abhishek Khandelwal <ak...@spikesource.com>.

On Thu, 2004-04-15 at 12:48, Stas Bekman wrote:
> Abhishek Khandelwal wrote:
> > On Thu, 2004-04-15 at 12:19, Stas Bekman wrote:
> > 
> >>Abhishek Khandelwal wrote:
> >>
> >>>I dont see any difference in two files.
> >>>
> >>>I runt the test twice to do a test coverage analysis.
> >>>At first, I install and test apache without test coverage
> >>>and then I again install and test with test-coverage enabled.
> >>>Second time, I get this error.
> >>
> >>Aha, you should have mentioned that in first place. In which case that's your 
> >>problem. With test-coverage enabled you don't get mod_access loaded. I don't 
> >>know why. Not an Apache-Test problem I think.
> > 
> > 
> > No, it is not related to code coverage. Since, I can run the test with
> > code coverage many a times. As I said, it occurs randomly without any
> > set pattern. So I dont know what exactly is causing this. 
> > And this problem occurs even when I have not enabled code coverage. 
> > The work around solution I got is I clean the test with t/TEST -clean,
> > remove the Makefile from test/perl-framework and the rebuild the test
> > with perl Makefile.PL option. When I do that, everythign goes smoothly.
> > 
> > The problem lies somewhere else.
> 
> Are you absolutely sure that the config doesn't change? Please do the real 
> check with diff on the whole t/conf directory if you didn't yet.


I see no difference in the config file. 

> 
> > What exactly is sticky configuration?
> 
> perldoc Apache::TestRun
> 
> and scroll to:
> 
> Persistent Custom Configuration
> 
> Please do this testing for me:
> 
> >>I doubt it has something to do with sticky configuration, but give it a try 
> >>and try to run with:
> >>
> >>APACHE_TEST_NO_STICKY_PREFERENCES=1 make test

I will do this test, but as I said, it is no confirmation that problem
is gone since it happens randomly. As I just ran the tests again without
any changes and it did run properly, both with and without coverage.

> 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com


Re: httpd test (perl-framework)

Posted by Stas Bekman <st...@stason.org>.
Abhishek Khandelwal wrote:
> On Thu, 2004-04-15 at 12:19, Stas Bekman wrote:
> 
>>Abhishek Khandelwal wrote:
>>
>>>I dont see any difference in two files.
>>>
>>>I runt the test twice to do a test coverage analysis.
>>>At first, I install and test apache without test coverage
>>>and then I again install and test with test-coverage enabled.
>>>Second time, I get this error.
>>
>>Aha, you should have mentioned that in first place. In which case that's your 
>>problem. With test-coverage enabled you don't get mod_access loaded. I don't 
>>know why. Not an Apache-Test problem I think.
> 
> 
> No, it is not related to code coverage. Since, I can run the test with
> code coverage many a times. As I said, it occurs randomly without any
> set pattern. So I dont know what exactly is causing this. 
> And this problem occurs even when I have not enabled code coverage. 
> The work around solution I got is I clean the test with t/TEST -clean,
> remove the Makefile from test/perl-framework and the rebuild the test
> with perl Makefile.PL option. When I do that, everythign goes smoothly.
> 
> The problem lies somewhere else.

Are you absolutely sure that the config doesn't change? Please do the real 
check with diff on the whole t/conf directory if you didn't yet.

> What exactly is sticky configuration?

perldoc Apache::TestRun

and scroll to:

Persistent Custom Configuration

Please do this testing for me:

>>I doubt it has something to do with sticky configuration, but give it a try 
>>and try to run with:
>>
>>APACHE_TEST_NO_STICKY_PREFERENCES=1 make test

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Re: httpd test (perl-framework)

Posted by Abhishek Khandelwal <ak...@spikesource.com>.
On Thu, 2004-04-15 at 12:19, Stas Bekman wrote:
> Abhishek Khandelwal wrote:
> > I dont see any difference in two files.
> > 
> > I runt the test twice to do a test coverage analysis.
> > At first, I install and test apache without test coverage
> > and then I again install and test with test-coverage enabled.
> > Second time, I get this error.
> 
> Aha, you should have mentioned that in first place. In which case that's your 
> problem. With test-coverage enabled you don't get mod_access loaded. I don't 
> know why. Not an Apache-Test problem I think.

No, it is not related to code coverage. Since, I can run the test with
code coverage many a times. As I said, it occurs randomly without any
set pattern. So I dont know what exactly is causing this. 
And this problem occurs even when I have not enabled code coverage. 
The work around solution I got is I clean the test with t/TEST -clean,
remove the Makefile from test/perl-framework and the rebuild the test
with perl Makefile.PL option. When I do that, everythign goes smoothly.

The problem lies somewhere else.

What exactly is sticky configuration?

> 
> > Moreover, this is just not doing with test-coverage.
> > It happens quite often and without any predictablility.
> > I am not sure how to reproduce it. Because it may or may not give me
> > this error.
> 
> We need to be able to reproduce it in order to fix it. If we can't we can't 
> fix it, since we don't know what the problem is.
> 
> I doubt it has something to do with sticky configuration, but give it a try 
> and try to run with:
> 
> APACHE_TEST_NO_STICKY_PREFERENCES=1 make test
> 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com


Re: httpd test (perl-framework)

Posted by Stas Bekman <st...@stason.org>.
Abhishek Khandelwal wrote:
> I dont see any difference in two files.
> 
> I runt the test twice to do a test coverage analysis.
> At first, I install and test apache without test coverage
> and then I again install and test with test-coverage enabled.
> Second time, I get this error.

Aha, you should have mentioned that in first place. In which case that's your 
problem. With test-coverage enabled you don't get mod_access loaded. I don't 
know why. Not an Apache-Test problem I think.

> Moreover, this is just not doing with test-coverage.
> It happens quite often and without any predictablility.
> I am not sure how to reproduce it. Because it may or may not give me
> this error.

We need to be able to reproduce it in order to fix it. If we can't we can't 
fix it, since we don't know what the problem is.

I doubt it has something to do with sticky configuration, but give it a try 
and try to run with:

APACHE_TEST_NO_STICKY_PREFERENCES=1 make test

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Re: httpd test (perl-framework)

Posted by Abhishek Khandelwal <ak...@spikesource.com>.
I dont see any difference in two files.

I runt the test twice to do a test coverage analysis.
At first, I install and test apache without test coverage
and then I again install and test with test-coverage enabled.
Second time, I get this error.

Moreover, this is just not doing with test-coverage.
It happens quite often and without any predictablility.
I am not sure how to reproduce it. Because it may or may not give me
this error.

Abhishek

On Thu, 2004-04-15 at 11:47, Stas Bekman wrote:
> [dropping the irrelevant CC address]
> 
> Abhishek Khandelwal wrote:
> > I am getting the following error when I run the perl-test framework.
> > I get this error when I run the test twice, one after another.
> > The first time, it goes thru properly and prints the summary of the
> > results.
> > But When I run for the second time, I get this error. I am using same
> > extra.conf in both the runs, but in second run, it fails. 
> > Anyone has any idea about what might be the reason for the error.
> > 
> > This is the error:::
> 
> > waiting 60 seconds for server to start: .Syntax error on line 16 of
> > /usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t/conf/extra.conf:
> > Invalid command 'Order', perhaps mis-spelled or defined by a module not included in the server configuration
> 
> Abhishek, the directive Order needs mod_access to be loaded. Is your server 
> built with mod_access built in or as a shared object?
> 
> What do you mean by running the test twice? Like so:
> 
> make test
> make test
> 
> In which case, save away t/conf after the first 'make test' and then when the 
> second time it fails compare the two directories (diff -ru t/conf.old t/conf). 
> Do you see any difference?
> 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com


Re: httpd test (perl-framework)

Posted by Stas Bekman <st...@stason.org>.
[dropping the irrelevant CC address]

Abhishek Khandelwal wrote:
> I am getting the following error when I run the perl-test framework.
> I get this error when I run the test twice, one after another.
> The first time, it goes thru properly and prints the summary of the
> results.
> But When I run for the second time, I get this error. I am using same
> extra.conf in both the runs, but in second run, it fails. 
> Anyone has any idea about what might be the reason for the error.
> 
> This is the error:::

> waiting 60 seconds for server to start: .Syntax error on line 16 of
> /usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t/conf/extra.conf:
> Invalid command 'Order', perhaps mis-spelled or defined by a module not included in the server configuration

Abhishek, the directive Order needs mod_access to be loaded. Is your server 
built with mod_access built in or as a shared object?

What do you mean by running the test twice? Like so:

make test
make test

In which case, save away t/conf after the first 'make test' and then when the 
second time it fails compare the two directories (diff -ru t/conf.old t/conf). 
Do you see any difference?

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

httpd test (perl-framework)

Posted by Abhishek Khandelwal <ak...@spikesource.com>.
I am getting the following error when I run the perl-test framework.
I get this error when I run the test twice, one after another.
The first time, it goes thru properly and prints the summary of the
results.
But When I run for the second time, I get this error. I am using same
extra.conf in both the runs, but in second run, it fails. 
Anyone has any idea about what might be the reason for the error.

This is the error:::
----------------------------------------------------------------------------------------------------------------------------------------------------

Manifying ../../blib/man3/HTTP::Date.3pm
Manifying ../../blib/man3/LWP::RobotUA.3pm
make[2]: Leaving directory `/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/httpd-test-bundle-0.02/libwww-perl-5.76'
make[1]: Leaving directory `/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/httpd-test-bundle-0.02'
Manifying blib/man3/Apache::TestConfigData.3pm
/opt/dev/apache/httpd/bin/httpd -d /usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t -f /usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t/conf/httpd.conf -DAPACHE2 -DPERL_USEITHREADS
using Apache/2.0.48 (prefork MPM)

waiting 60 seconds for server to start: .Syntax error on line 16 of
/usr/local/nightly/cvs-root/oss/core/webserver/httpd/test/perl-framework/t/conf/extra.conf:
Invalid command 'Order', perhaps mis-spelled or defined by a module not included in the server configuration
!!! 
server has died with status 255 (please examine t/logs/error_log)

--------------------------------------------------------------------------------------------------------------------------------------------


Thanks,
Abhishek