On Tue, 23 Nov 2004, Joe Orton wrote:
> Discussion of whether or not it's useful to have PHP tests in httpd-test
> can take place on test-dev@, please send your comments there and I'll
> follow up.
I actually think it's useful to have php tests in our suite, because
having a large number of tests
On Thu, 28 Oct 2004, Geoffrey Young wrote:
> I get the following failures on 1.3.32 but not on 1.3.33.
>
> t/modules/rewrite.t 222 9.09% 18 20
> t/security/CAN-2004-0940.t11 100.00% 1
> t/security/CAN-2004-0958.t92 22.22% 1 3
>
On Wed, 29 Sep 2004 [EMAIL PROTECTED] wrote:
> jorton 2004/09/29 08:03:59
>
> Modified:perl-framework/c-modules/test_pass_brigade
> mod_test_pass_brigade.c
> Log:
> Prevent death by memory consumption in an --enable-pool-debug/-lefence
> build: allocate and
On Sun, 4 Apr 2004, Stas Bekman wrote:
> Cool, can you patch it so that it'll check first whether it can do that,
> before it does that? We get users reporting problems when ulimit fails. I
> don't have an access to Solaris, so if you can fix that, that would be great.
> Thanks.
>
> I guess it nee
On Mon, 5 Apr 2004 [EMAIL PROTECTED] wrote:
> stas2004/04/04 21:35:21
>
> Modified:perl-framework/Apache-Test/lib/Apache TestRun.pm
> TestConfig.pm
>perl-framework/Apache-Test Changes
> Log:
> Don't try to set ulimit unlimited for coredumps
On Thu, 8 Jan 2004, Donald Doane wrote:
> The following comment is from apr_lib.h:
>
> * apr_vformatter does not call out to any other code, it is entirely
> * self-contained. This allows the callers to do things which are
> * otherwise "unsafe". For example, apr_psprintf uses the "scratch"
>
Where does it say that? httpd uses it extensively, so if it's not, I'd
tend to think we'd have noticed by now...
--Cliff
On Thu, 8 Jan 2004, Donald Doane wrote:
> Okay, will do that, but it's called in
> "flood_easy_reports::easy_process_stats()" and it seems APR
> documentation implies it is
On Wed, 10 Dec 2003, Geoffrey Young wrote:
> oh, and I'm very impressed with the thoroughness of the tests, btw. nice
> work.
That's what happens when you keep adding more and more tests and you STILL
get people reporting failure cases. Sigh.
Thanks though. :-)
--Cliff
On Mon, 8 Dec 2003, Geoffrey Young wrote:
> > Sounds like a cvs conflict marker.
> duh. that was it. eesh.
I only knew that because it happens to me all the time. ;) nbd.
--JC
On Mon, 8 Dec 2003, Geoffrey Young wrote:
> >>Use of bare << to mean <<"" is deprecated at modules/include.t line 120.
> >>
> >>which is probably new to 5.8.2.
> >
> >
> > Interesting. << doesn't occur within include.t. So it happens within the
> > framework?
>
> hmm, perhaps. I was actually plan
On Thu, 13 Nov 2003, Norman Tuttle wrote:
> How do the pools define "if possible" in your wording below (i.e., how
> would the pool know when to reuse memory)?
It's kind of complicated, so I don't know how well I can explain it off
the top of my head (Sander, feel free to jump in here :), but it
On Thu, 13 Nov 2003, Norman Tuttle wrote:
> around without generating any data, and (3) that the data (timings, in
> particular) itself seems to be suspect when we are in the process of
> "hitting the rail". I was wondering whether (1) other people have seen
> this issue with this or other applica
On Thu, 23 Oct 2003, Jacek Prucia wrote:
> then prepare separate patch and post it here. You'll score extra points
> from our own style purist (Hello Justin ;)
...and hello me, too. ;)
--Cliff "Style Police" Woolley
On Wed, 15 Oct 2003 [EMAIL PROTECTED] wrote:
> fix link error with apr 1.0
>
> -trailer_header = ap_table_get(r->headers_in, "X-Chunk-Trailer");
> +trailer_header = apr_table_get(r->headers_in, "X-Chunk-Trailer");
I fixed this in my local tree yesterday but then forgot about it. It
On Thu, 2 Oct 2003, Jeffrey P. Toth wrote:
> Can someone tell me how to unsubscibe from this list. I have sent emails
> to all addresses and they are just returned. Thank you.
If you'd look in the headers of any message delivered to this list, you'd
see:
-
> is a safe bet. If this looks really obscure considering APR concepts, then
> please feel free to commit a fix.
Fix commited. Please test, since I didn't. :)
PS: I also fixed a buglet or two.
--Cliff
On Sun, 7 Sep 2003 [EMAIL PROTECTED] wrote:
> +if (apr_procattr_create(&procattr, rp->pool) != APR_SUCCESS) {
> +apr_file_printf(local_stderr,
> +"apr_procattr_create failed for '%s'\n",
> +rp->url[rp->current_url]
On Thu, 4 Sep 2003, Stas Bekman wrote:
> it probably doesn't make any difference if older releases won't work
> with it.
+1. As long as the top-of-tree 1.3-dev, 2.0-dev, and 2.1-dev all build
and run, that's fine. Older point releases are not an issue.
On Wed, 9 Jul 2003, Stas Bekman wrote:
> plan ..., have_apache2 && have_apache_mpm('prefork');
I think this is probably the way to go. If you call have_apache_mpm() and
it's apache 1.3, I might have it return an error of some kind, but I
wouldn't have it return 'prefork'.
--Cliff
On Fri, 7 Feb 2003, Stas Bekman wrote:
> I haven't seen any activity with maintaining tests in a while and I have a
> bunch of ssl tests failing. I remember Ryan working on a new test suite.
> What's the current status of things? Should Joe's new php tests be committed?
>
> These fail for me:
>
>
On Thu, 30 Jan 2003, William A. Rowe, Jr. wrote:
> That's actually sorta sad... are they missing CRYPTO_malloc_init as well?
[EMAIL PROTECTED]:../build/Crypt-SSLeay-0.45# grep -i CRYPTO_malloc_init *
[EMAIL PROTECTED]:../build/Crypt-SSLeay-0.45#
Looks that way, yeah... :)
--Cliff
Figured it out. It was a bug in Crypt::SSLeay ... not sure how it ever
even worked. I'm sending them the following patch:
--- SSLeay.xs.orig 2002-08-01 17:43:22.0 -0400
+++ SSLeay.xs 2003-01-29 21:41:17.0 -0500
@@ -109,6 +109,7 @@
SSLeay_add_all_algorithms
On Wed, 29 Jan 2003, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote:
> PS : I'm using Perl 5.8 though (I'm not sure if it matters, but I can
> try on 5.6.1)
I'm using Linux, Slackware current, kernel 2.4.20, glibc 2.3.1, openssl
0.9.6h, perl 5.8.0, latest Crypt::SSLeay.
--Cliff
Has anybody out there managed to get Crypt::SSLeay to do anything but
segfault with recent OpenSSL's? I sure can't. As a result, every single
SSL test fails for me.
--Cliff
On Thu, 7 Nov 2002, William A. Rowe, Jr. wrote:
> Guys, some time in the {recent} past, TEST.pl was renamed TEST.
Umm it's actually been TEST for as long as I can remember.
Here's a partial directory listing of an old copy of httpd-test of mine:
-rwxr-xr-x1 jcw5qroot 424 Ju
On Mon, 3 Jun 2002, Aaron Bannert wrote:
> Cliff is always mentioning something like t/TEST -d gdb or something
> like that. Won't that run in -X mode automatically?
Yeah, that works quite well. Have two consoles open, run t/TEST -d gdb in
one of them (which automatically runs in -X mode and att
On Fri, 31 May 2002, Doug MacEachern wrote:
> seems that the test suite now requires httpd-2.0-cvs from
> HEAD? server does not start with 1.3.x or 2.0.36:
>
> Syntax error on line 139 of .../t/conf/extra.conf RewriteMap: map file
> or program not found:/.../t/htdocs/modules/rewrite/append.pl foo
Now that the SSLLog is combined with the regular log, and since we run at
full debug loglevel, the error_log is growing too fast. One run through
t/TEST on my system gives about 60MB worth of error_log. No problem
there. BUT, when you run t/SMOKE and get more than 40 times that many
tests run (
works. :)
--Cliff
--
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
object save
run 't/TEST -clean' to clean up before continuing
And yes, I've cvs up'ed, make clean'ed, and all that jazz.
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
Sorry about the flurry of commit messages... I'm just rearranging t/htdocs
a bit to get a more parallel directory structure to make it easier to add
other stuff without cluttering up the docroot.
--Cliff
--
Cliff Woolley
[
,v files. But it's really not that big a deal anyhow, you
can leave it as-is if you like.
--Cliff
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
itters? If so, great!
Yep! It's a subproject. All core httpd developers are already in avail
for httpd-test.
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
On Tue, 16 Apr 2002, Stas Bekman wrote:
> one last question. Should the ssl certificates be recreated on t/TEST
> -clean (or 'make test')?
As they're currently done, they need to be recreated at least *once* in a
while, because they're set to expire. That happened on me once when I
hadn't cleane
estSmoke.pm:373: Unknown command paragraph
"= Summary
==="
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
too hard. GO PARTY! ;)
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
related
to the version of LWP I'm using?
--Cliff
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
they both work. :) Anyway, I'll go ahead and
change the README back to what it was before.
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
directory
So I guess I'm confused as to where the trouble is.
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
a t/TEST -clean?
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
pected: 200
# received: '200'
ok 88
# testing : Explicitly request fu/two/index.fu.html
# expected: 200
# received: '200'
ok 89
# testing : Verify with a default language Accept-Language still obeyed
# expected: 'index.html.fu'
# received: 'index.html.fu'
ok 90
# testing : Verify with a default language Accept-Language still obeyed
(compression on)
# expected: 'index.html.fu.gz'
# received: 'index.html.fu.gz'
ok 91
# testing : Verify with a default language Accept-Language still obeyed
# expected: 'index.fu.html'
# received: 'index.fu.html'
ok 92
# testing : fu has a higher quality rating, so we expect fu
# expected: 'index.html.fu'
# received: 'index.html.fu'
ok 93
# testing : fu has a higher quality rating, so we expect fu
# expected: 'index.fu.html'
# received: 'index.fu.html'
ok 94
# testing : fu has a higher quality rating, so we expect fu
# expected: 'index.html.fu.gz'
# received: 'index.html.fu.gz'
ok 95
# testing : bu has the highest quality but is non-existant, so fr is next best
# expected: 'index.html.fr'
# received: 'index.html.fr'
ok 96
# testing : bu has the highest quality but is non-existant, so fr is next best
# expected: 'index.fr.html'
# received: 'index.fr.html'
ok 97
# testing : bu has the highest quality but is non-existant, so fr is next best
# expected: 'index.html.fr.gz'
# received: 'index.html.fr.gz'
ok 98
FAILED tests 1-3, 24-26, 70-72
Failed 9/98 tests, 90.82% okay
Failed Test Status Wstat Total Fail Failed List of Failed
modules/negotiation.t 989 9.18% 1-3, 24-26, 70-72
--
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
, start the server in the debug mode";
-error "@_ ($log_file_info)";
+error("@_ ($log_file_info)");
}
sub start {
@@ -397,7 +397,7 @@
unless (-x $httpd) {
my $why = -e $httpd ? "is not executable" : "does not exist";
-error "cannot start server: httpd ($httpd) $why";
+error("cannot start server: httpd ($httpd) $why");
return 0;
}
@@ -422,7 +422,7 @@
}
while ($old_pid and $old_pid == $self->pid) {
-warning "old pid file ($old_pid) still exists";
+warning("old pid file ($old_pid) still exists");
sleep 1;
}
--
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
46
fail #17
# testing : TIME_WDAY
# expected: 6
# received: '6'
ok 18
--
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
. What you want is this:
foo.sh >/tmp/foo.log 2>&1
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
ge DoS hole.
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
d.
BTW, this mailing list is for issues relating to development of the test
suite for Apache. Please direct this type of question to one of the
support mailing lists in the future.
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
eem to get anything
but a 500 out of /modules/cgi/perl.pl, with GET or HEAD. For all I can
tell, it's a legitimate bug with the httpd, because I get a 500 when I try
it by hand as well. Anyone else seen this?
--Cliff
------
Cliff Wo
at's one thing I didn't try... I'll re-check-out and see what
happens.
--Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
t;;
print "perl cgi";
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
utility called "pod2html" ... :-)
--Cliff
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
t none of them have really BIG
content... not even close to big enough to warrant a brigade split. Maybe
we should add a test that includes biggish data from the middle of a
biggish file? Somewhere around 32k should be sufficient, I'd guess...
--Cliff
----------
ow in a test with an absolute path as well?
Thanks,
Cliff
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
ative
path. So can someone please add a test or two to the mod_include tests,
sticking some file in a subdirectory of t/htdocs/modules/include and
trying to include that file from, say, big.shtml in the main directory?
Thanks,
Cliff
-
s on HEAD?
Thanks,
Cliff
------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
and you might get even closer to something
testable, though it'd arguably be better if the load were pool-use-heavy.
--Cliff
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
> +apr_bucket_copy(ec, &foo);
>}
> APR_BRIGADE_INSERT_TAIL(bsend, foo);
>ec = APR_BUCKET_NEXT(ec);
>
>
>
>
--
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
s exactly the problem. All good now.
Thanks!
--Cliff
PS: All tests pass on Apache/2.0.25-dev! Woohoo!!! =-)
----------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
rd to distinguish the "good" errors from the "bad" errors,
especially since you can't run just a single test number...
> might be worth posting to the test-dev list, john sachs who wrote the test
> might have some ideas.
Here goes...
Thanks,
Cliff
---
58 matches
Mail list logo
