It's on my short list to auto-generate the rsync.conf file. As soon as that's
done,
things like this will just happen for us. In the meantime, just send a note to
Brian,
and he'll add it.
Ryan
On Thursday 09 August 2001 09:47, Stas Bekman wrote:
> On Thu, 9 Aug 2001, Ryan Bloom wrote:
> > On
Thanks.
On Thu, 9 Aug 2001, john sachs wrote:
> ah.
> i see where this is going.
> i will make the fix.
> -j
>
> On Thu, Aug 09, 2001 at 06:06:41PM +0100, Gary Benson wrote:
> +
> + What does "httpd -V | grep DEFAULT_ERRORLOG" say in your setup?
> +
> + On Thu, 9 Aug 2001, john sachs wrote:
> +
ah.
i see where this is going.
i will make the fix.
-j
On Thu, Aug 09, 2001 at 06:06:41PM +0100, Gary Benson wrote:
+
+ What does "httpd -V | grep DEFAULT_ERRORLOG" say in your setup?
+
+ On Thu, 9 Aug 2001, john sachs wrote:
+
+ > the test finds my error log ok...
+ >
+ > On Thu, Aug 09, 2001
What does "httpd -V | grep DEFAULT_ERRORLOG" say in your setup?
On Thu, 9 Aug 2001, john sachs wrote:
> the test finds my error log ok...
>
> On Thu, Aug 09, 2001 at 05:39:20PM +0100, Gary Benson wrote:
> +
> + Does the test itself work correctly for you, though? I have to have my
> + patched ve
the test finds my error log ok...
On Thu, Aug 09, 2001 at 05:39:20PM +0100, Gary Benson wrote:
+
+ Does the test itself work correctly for you, though? I have to have my
+ patched version for it to be able to find the error_log.
+
+ Gary
+
+ On Thu, 9 Aug 2001, john sachs wrote:
+
+ [snip]
+ >
On Fri, 10 Aug 2001, Stas Bekman wrote:
> On Thu, 9 Aug 2001, Ryan Bloom wrote:
>
> > On Thursday 09 August 2001 05:10, Stas Bekman wrote:
> > > * 'cvs co -c' doesn't include httpd-test module, only apachetest, which
> > > includes Apache-Test only.
> >
> > We don't keep `cvs co -c` up to date.
On Thu, 9 Aug 2001, Ryan Bloom wrote:
> On Thursday 09 August 2001 05:10, Stas Bekman wrote:
> > * 'cvs co -c' doesn't include httpd-test module, only apachetest, which
> > includes Apache-Test only.
>
> We don't keep `cvs co -c` up to date. Brian believes this encourages
> people to check out ev
Does the test itself work correctly for you, though? I have to have my
patched version for it to be able to find the error_log.
Gary
On Thu, 9 Aug 2001, john sachs wrote:
[snip]
> that text was getting dumped into the error_log with the build of
> PHP/4.0.4pl1 i had. but apparently that may no
On Thu, 9 Aug 2001, Paul Edgar wrote:
> modules/expires.Undefined subroutine &HTTP::Request::Common::HEAD
btw, this should work without lwp installed, i will look into that.
yeah,
i had a build of php that worked that way, but i also had one that didnt. i
dont really know how php is supposed to work in this situation. (thats the
reason for the comment in the code...heh)
this is supposed to be testing the register_shutdown_function(). the way the
test is set up,
On Thu, 9 Aug 2001, Paul Edgar wrote:
> After verifying that I can connect to apache 2.0 with a web browser,
> when running the test I am seeing the following problem. Anyone else
> see this problem.
>
> using Apache/2.0.18 (threaded MPM)
> waiting for server to warm up...ok
> server localhost:8
install LWP.
-j
Hi all,
Test 2 of 2 in t/php/func5.t does not correctly locate the logfile -- I
don't know if it is just my setup or what. Anyway, the patch below makes
the test use the same variable that is used during generation of
t/conf/httpd.conf in Apache-Test/lib/Apache/TestConfig.pm.
Even now I have it
After verifying that I can connect to apache 2.0 with a web browser,
when running the test I am seeing the following problem. Anyone else
see this problem.
using Apache/2.0.18 (threaded MPM)
waiting for server to warm up...ok
server localhost:8529 started (pid=2378)
modules/expires.Undefined
On Thursday 09 August 2001 05:10, Stas Bekman wrote:
> * 'cvs co -c' doesn't include httpd-test module, only apachetest, which
> includes Apache-Test only.
We don't keep `cvs co -c` up to date. Brian believes this encourages people to
check out everything all at once, which puts an undue strain
On Thu, 9 Aug 2001, Doug MacEachern wrote:
> On Thu, 9 Aug 2001, Gary Benson wrote:
>
> > | skip !&ExtModules::TestEnv::has_php4, GET_BODY("/php/add.php") eq '6';
>
> that only skips one test in a test file, so if you plan 60 php tests in a
> single file, you have to test that condition 60 times.
On Thu, 9 Aug 2001, Gary Benson wrote:
> | skip !&ExtModules::TestEnv::has_php4, GET_BODY("/php/add.php") eq '6';
that only skips one test in a test file, so if you plan 60 php tests in a
single file, you have to test that condition 60 times. not good.
Apache::Test::plan lets you skip every test
In httpd-test's perl-framework tests, Apache::Test::plan is a wrapper
around Test::plan. Apache::Test::plan allows you to have a condition as
the last argument of the plan call; if the condition is not met, the test
is skipped. A test which will only be run if we have php4 looks like this:
| plan
> > > I tried this once, for the lexical parser in a desktop calculator program
> > > I wrote. It is a really liberating experience, and leads to greater
> > > experimentation.
> >
> > the only problem is that usually to write some more advanced tests, you
> > actually need to have some working cod
* 'cvs co -c' doesn't include httpd-test module, only apachetest, which
includes Apache-Test only.
* I've just commited the documentation for these testing options:
t/TEST -times=N -order=(repeat|rotate|random)
which you should definitely try and get surprised as some tests that have
passed
On Thu, 9 Aug 2001, Stas Bekman wrote:
> On Thu, 9 Aug 2001, Gary Benson wrote:
>
> > On Thu, 9 Aug 2001, Stas Bekman wrote:
> >
> > > Some methods of extreme programming suggest writing tests even before
> > > the code have been written
> >
> > I tried this once, for the lexical parser in a desk
On Thu, 9 Aug 2001, Gary Benson wrote:
>
> On Thu, 9 Aug 2001, Stas Bekman wrote:
>
> > Some methods of extreme programming suggest writing tests even before
> > the code have been written
>
> I tried this once, for the lexical parser in a desktop calculator program
> I wrote. It is a really liber
On Thu, 9 Aug 2001, Stas Bekman wrote:
> Some methods of extreme programming suggest writing tests even before
> the code have been written
I tried this once, for the lexical parser in a desktop calculator program
I wrote. It is a really liberating experience, and leads to greater
experimentatio
On Wed, 8 Aug 2001, Ryan Bloom wrote:
>
> > Especially important to make sure that those who code the modules know
> > about the existance of this project and the best way to proceed is to do
> > the following:
> >
> > - every time a bug gets reported, before you even attempt the fix, write a
> >
> Especially important to make sure that those who code the modules know
> about the existance of this project and the best way to proceed is to do
> the following:
>
> - every time a bug gets reported, before you even attempt the fix, write a
> test that exposes the bug.
> - now fix the bug and m
> On Wed, Aug 08, 2001 at 10:28:24AM +0800, Stas Bekman wrote:
> +
> + OK, so why not to do: /^[1-6]$/ ?
>
> this wouldnt test for the right thing.
>
> + I'd do it even more flexible:
> +
> + my $pat = join '', @num;
> + /^[$pat]$/
> +
> + so now you can change @num and not to worry about forgettin
hello.
i think these errors are because you do not have LWP installed on you system.
try installing LWP. (http://search.cpan.org/search?dist=libwww-perl).
sorry, the doc is probably not clear yet on all the system requirements...
-j
On Wed, Aug 08, 2001 at 09:21:41AM -0500, Paul Edgar wrote:
+
+
27 matches
Mail list logo
