On Wed, 27 Jun 2001, Stas Bekman wrote:
> have you tried to random stress test? Did you see what I've seen?
not yet, i want to figure out the current cgi #3 problem before moving on.
> I've read your email about inlining after I've sent the other patch. Will
> do the inlining from now on.
co
On Tue, 26 Jun 2001, Doug MacEachern wrote:
> On Wed, 27 Jun 2001, Stas Bekman wrote:
>
> > I've seen this too. Are you sure it has anything to do with the patch?
> > the patch just shuffles the tests. This error seem to be of a different
> > source. Can you reproduce this behavior on demand? Onc
On Wed, 27 Jun 2001, Stas Bekman wrote:
> I've seen this too. Are you sure it has anything to do with the patch?
> the patch just shuffles the tests. This error seem to be of a different
> source. Can you reproduce this behavior on demand? Once I've restarted the
> server I didn't see this error
On Wed, 27 Jun 2001, Stas Bekman wrote:
> On Tue, 26 Jun 2001, Doug MacEachern wrote:
>
> > patch looks good stas, but for some reason it now tries to run modules/cgi
> > a bunch of times, which doesn't happen with any other tests:
> >
> > modules/cgi..ok 2/6Confused test output: test 2 a
On Tue, 26 Jun 2001, Doug MacEachern wrote:
> patch looks good stas, but for some reason it now tries to run modules/cgi
> a bunch of times, which doesn't happen with any other tests:
>
> modules/cgi..ok 2/6Confused test output: test 2 answered after
> test 2
> modules/cgi..ok 2/6
for those who don't have mailers that will mangle inline patches, please
send patches inline rather than as attachments, makes it much easier to
comment on the patch. thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For add
patch looks good stas, but for some reason it now tries to run modules/cgi
a bunch of times, which doesn't happen with any other tests:
modules/cgi..ok 2/6Confused test output: test 2 answered after
test 2
modules/cgi..ok 2/6Confused test output: test 2 answered after
test 2
modul
This patch introduces these changes:
* new flag: --times=N run the tests N times
* new flag: --order=order run the tests in the random order, rotate or
repeat them
* when the random order is specified, the seed will be taken from
APACHE_TEST_SEED env var or autogenerated and printed to
On Wed, 27 Jun 2001, Stas Bekman wrote:
> yours?
% uname -a
Linux mako.covalent.net 2.2.16-22 #7 Wed Mar 28 15:39:46 PST 2001 i686 unknown
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
On Wed, 27 Jun 2001, Stas Bekman wrote:
> As usual, I mess things up :( sorry about that. I meant 'autogenerated
> docs'.
no problem :)
> Currently we don't have autogenerated docs, right? I was just thinking how
> 'make docs' should invoke other utils to create these autogenerated docs,
> be
On Tue, 26 Jun 2001, Doug MacEachern wrote:
> On Tue, 26 Jun 2001, Stas Bekman wrote:
>
> > it still doesn't work, even with this patch. What's is the difference in
> > your dev environment? I have all cvs versions perl/apache/mod_perl on
> > linux. Scan.pm from your site with this patch. The on
On Tue, 26 Jun 2001, Doug MacEachern wrote:
> On Tue, 26 Jun 2001, Stas Bekman wrote:
>
> > let's try to go with the inlines first, if we see that it's not good. we
> > extract all the inlines into the separate .pod files. This is something
> > that we can do much easier than the reverse operatio
On Tue, 26 Jun 2001, Doug MacEachern wrote:
> On Tue, 26 Jun 2001, Stas Bekman wrote:
>
> > let's try to go with the inlines first, if we see that it's not good. we
> > extract all the inlines into the separate .pod files. This is something
> > that we can do much easier than the reverse operatio
On Tue, 26 Jun 2001, Stas Bekman wrote:
> it still doesn't work, even with this patch. What's is the difference in
> your dev environment? I have all cvs versions perl/apache/mod_perl on
> linux. Scan.pm from your site with this patch. The only thing I had to
> install was Data::Flow, and my ve
On Tue, 26 Jun 2001, Stas Bekman wrote:
> what do you think about this para about default sorting?
>
> > I understand. Another option would be to always sort the
> > tests unless you have specified their order on the
> > command line.
> >
> > o if you specify none -- everything is sorted.
> > o
On Tue, 26 Jun 2001, Stas Bekman wrote:
> let's try to go with the inlines first, if we see that it's not good. we
> extract all the inlines into the separate .pod files. This is something
> that we can do much easier than the reverse operation, assuming that we
> want the snippets of pod to be
16 matches
Mail list logo
