On Thu, 21 Jun 2001, Doug MacEachern wrote:
> On Thu, 21 Jun 2001, Geoffrey Young wrote:
>
> > since Apache::Test seems to be the hot topic of late, I was wondering if I
> > could make a few (well, two) requests :)
> >
> > 1. I tried to implement skip() functionality, but couldn't get my head
> >
> -Original Message-
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 21, 2001 12:22 PM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: Apache::Test request
>
>
> On Thu, 21 Jun 2001, Geoffrey Young wrote:
>
> > since Apache::Test seems to be the
On Thu, 21 Jun 2001, Geoffrey Young wrote:
> since Apache::Test seems to be the hot topic of late, I was wondering if I
> could make a few (well, two) requests :)
>
> 1. I tried to implement skip() functionality, but couldn't get my head
> around it. its probably an important component to have
On Thu, 21 Jun 2001, Stas Bekman wrote:
> --
> Run:
> $ ./t/TEST --run-tests
> $ ./t/TEST --run-tests modules/cgi.t
>
> the second time modules/cgi.t is run, test #3 fails.
i see that too, not looked into it yet.
> Me thinking: if the test reports ok on the first run, but fai
On Thu, 21 Jun 2001, Stas Bekman wrote:
> argh, building mod_perl on a different machine I've realized that the
> problem didn't go away. It's still there after all the updates.
go ahead and commit, util_date.h went away when date functions moved to
apr-util. i've change my build script to blo
On Wed, 20 Jun 2001, Randy Kobes wrote:
> Hi,
> Apache on Win32, when installed, also copies the header and
> lib files to the target install directory. The attached diff against the
> cvs Makefile.PL allows this install location to be entered as the
> Makefile.PL argument APACHE_SRC. The
since Apache::Test seems to be the hot topic of late, I was wondering if I
could make a few (well, two) requests :)
1. I tried to implement skip() functionality, but couldn't get my head
around it. its probably an important component to have eventually.
2. the current logic is broken for 1.3 wh
--
Run:
$ ./t/TEST --run-tests
$ ./t/TEST --run-tests modules/cgi.t
the second time modules/cgi.t is run, test #3 fails.
Me thinking: if the test reports ok on the first run, but fails on the
second, should we change the way tests are run? rerun tests
twice to make sure that the
