Stas Bekman wrote:
I'd like to get a new A-T out of the door. There were a *lot* of tweaks
and new features added since the last release. It'd be nice to see
whether users are happy with them, before we get a new mp2 release out.
sounds like a plan.
--Geoff
$vars-{proxyssl_url} ||= '';
+$self-{defines} ||= '';
oops, make that $vars :)
--Geoff
Joe Orton wrote:
On Fri, Feb 20, 2004 at 01:30:03PM -0500, Geoffrey Young wrote:
is there really no way to pass additional -D switches to the server? I
can't see any, so unless I'm missing it...
Ooh, cool, I tried to add that feature earlier in the week too (and
didn't come up
-$file ||= 'SKIP';
+$file ||= 't/SKIP';
excellent, thanks for tracking that down.
we just need to be a bit more platform independent. if you could verify
that the attached patch works ok for you, I'll commit it.
--Geoff
Index: lib/Apache/TestHarness.pm
1. is it possible to run the suite *without* doing a 'make install'?
in my development environment i discovered that i had to do that
in order oget rid of some cruft left behind from having done a
'make install' in the past. however, i'd prefer to not have to
force the
-$file ||= 'SKIP';
+$file ||= catfile Apache::Test::vars('serverroot'), 'SKIP';
oops. forgot to add the class up top. guess I'm not quite with it today yet :)
--Geoff
Index: lib/Apache/TestHarness.pm
===
RCS file:
-$file ||= 'SKIP';
+$file ||= catfile Apache::Test::vars('serverroot'), 'SKIP';
Geoff, you are making a good point of removing the hardcoding of t/
towards the idea of being able to split the test suite.
well, it's an idea that we're all working toward, yourself included :)
t/modules/expires.t924 4.35% 13 21 33 45
14 subtests skipped.
and that's it.
oh, I see what you mean, you're missing the
Failed 1/1 test scripts, 0.00% okay. 1/1 subtests failed, 0.00% okay.
line.
are you using an older version of perl perhaps?
yep,
Stas Bekman wrote:
We would like to release Apache::Test 1.08. It includes multiple changes
and improvements, therefore we need your help to test it and report any
problems you may have noticed.
http://apache.org/~stas/Apache-Test-1.08-dev.tar.gz
I'm getting a strange error from 5.6.1
sub config_defines {
+my $self = shift;
+
my @defines = ();
for my $item (qw(useithreads)) {
@@ -88,7 +90,9 @@
push @defines, -DPERL_\U$item;
}
-push @defines, map { -D$_ } split ,
shift-{config}-{vars}-{defines};
+if
in my case, it's possibly my wrapper that's gobbling the line. for
pity's sake, why it that going to stderr when everything else is going to
stdout?
erk. now i'm seeing it, but *only* if all of the tests are successful.
i need to see it regardless, and including the
Bail out!
to standard output. Any message after these words will be
displayed
by Test::Harness as the reason why testing is stopped.
I haven't tested whether this really works in A-T, but I see no reason
why it shouldn't.
I tried to use it when I was
so, it looks like an issue with your wrapper and not A-T
core, yes?
no. if i run only a test script that passes completely, i get
t/modules/accessok
All tests successful.
Files=1, Tests=408, 4 wallclock secs ( 3.13 cusr + 0.43 csys = 3.56 CPU)
if i run only a script that fails,
Stas Bekman wrote:
The following patch, allows a graceful exit from 'make test' (so that
CPAN.pm and other clients can continue w/ installation) if users fail to
provide the path to httpd or running under root and we figure out that
apache can't access the files w/ nobody (or some other
$ENV{APACHE_TEST_STARTUP_TIMEOUT} now supersedes -startup_timeout
[...]
What's the reason for this change?
it was a follow up from something on modperl@
I almost always expect that command
line arguments supercede env variables.. i.e.
$ CVSROOT=foo cvs -d bar co foo
Bad CVSROOT:
+my $dversion = $self-server-dversion;
+if ($dversion eq '-DAPACHE1') {
that's '-D APACHE1' in current cvs, no?
--Geoff
hi all
I'm _still_ having problems with sticky preferences. unfortunately, I don't
have the time atm to locate the specifics, but basically I was trying to
compile a 1.3 static build (without mod_so) using -httpd. while A-T found
the proper httpd, LoadModule statements that pointed to my last
Stas Bekman wrote:
Rodent of Unusual Size wrote:
Stas Bekman wrote:
does this make any difference/
perl Makefile.PL -apxs K:/Coar/Apache/Server-1.3/bin/apxs.pl -httpd
K:/Coar/Apache/Server-1.3/bin/Apache.exe
yes, it made a difference -- but it still didn't work. it now
specifies
% t/TEST -help
...
and in case it's not obvious (and for the archives) the '...' represents a
slurry of options from TestRun.pm, whereas the shown 'configuration options'
represent those from TestConfig.pm. I was wondering where -preamble and
some others were and it took me a minute :)
Rodent of Unusual Size wrote:
Rodent of Unusual Size wrote:
specifically what operations need make or nmake? i need to
know so i can provide appropriately-prepared files so it
won't try to run it. this is so i can run it on systems
that don't have a developer environment installed..
Rodent of Unusual Size wrote:
Randy Kobes wrote:
If you put the compiled modules in place, and then run
'nmake test', is the problem that things get cleaned out
first (erasing the binaries), or that it just tries to
recompile things? On my system (which has VC++), 'nmake
test' first cleans
Something is not right here, Geoff. It require()s *only* if
IS_MOD_PERL_2 is true. Which must have Apache::Build present. I suggest
that you try to revert it and find the real cause of the problem, rather
than hide it. Thanks.
ah, I see what's going on. I removed all Apache stuff but
right, I think I got that. but that requires knowing the hard-coded
path.
That's what Ken wanted
ok, but just because you get substitution doesn't mean you have to use it :)
perhaps I wasn't clear enough, but the proposed httpd.extra.conf.in
would be
appended to the generated
By splicing you mean 'Include ken_extra.conf' from t/conf/httpd.conf?
Yes, but have_module() doesn't look it up in any of the conf files, it
looks it up from the config object $cfg-{modules} which get populate
with available modules when the config is generated, and it only scans
the
ok t_cmp (
undef,
get_undef,
Retrieve undef from subroutine
);
# expected: undef
# received: Retrieve undef from subroutine
not ok 1
get_undef is slurping up the text as an argument. call it as get_undef()
instead (nobody really uses the
Geoffrey Young wrote:
ok t_cmp (
undef,
get_undef,
Retrieve undef from subroutine
);
# expected: undef
# received: Retrieve undef from subroutine
not ok 1
get_undef is slurping up the text as an argument. call it as get_undef()
instead
I like that idea of adopting all of T::M. However, does T::M have a
comparable function to t_cmp that gives the expected and received
values? I *really* like the verbose output that t_cmp gives!
is() is similar in many ways to t_cmp() except it doesn't support array
comparisons, regular
The main problem is the dependency which we we don't want to create in
Apache-Test.
yes, I agree. but I think that something like this would be great, as it
would keep users from needing to jump through a bunch of hoops just to
prevent redefined warnings.
--Geoff
Index: lib/Apache/Test.pm
whichever is fine with me. Though please explain where did you take that
standard from? I think most modules follow the followinig import
convention:
- a word 'foo' usually means symbol and you'd expect to be able to use
it in a form of ([EMAIL PROTECTED])foo.
- a tag ':foo' means,
hi all
I've managed to figure out at least preliminary support for using Test::More
as the backend for Apache::Test. attached is a patch as well as a tarball
that uses a few Test::More features in it. I may have missed a few of the
finer features of Test::More, but it seems to do what I need it
I don't understand why did you have this problem (what did you have in
@INC?), but I think that this just works around the problem. It's better
to go up to where $self-{inc} is getting set and not let invalid values
in, so if you use $self-{inc} you won't have to workaround again.
I was
hi all
a while ago Ken Coar brought up that Apache-Test doesn't print the final
test count when there are errors. that is, we currently do this:
# Failed test 20 in t/apache/contentlength.t at line 54 fail #10
FAILED tests 2, 6, 10, 14, 16, 18, 20
Failed 7/20 tests, 65.00% okay
Failed
Not sure what you are talking about above, the only difference between
the two is in line:
blarg, cut and paste error.
without my patch, it looks like this (note it's 1.3)
[EMAIL PROTECTED] perl-framework]$ t/TEST t/apache/contentlength.t -v
/apache/1.3/dso/perl-5.8.4/bin/httpd -d
Got it. Why not just do this:
return unless $_[0] =~ /^Failed/i; #dont catch Test::ok failures
+print $_[0];
truthfully, I spent far too long trying to figure out why the die() wasn't
cascading. once I got it I just patched it and let the patch fly without
too much
For example this
does the trick:
Index: Apache-Test/lib/Apache/TestRun.pm
===
RCS file:
/home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/TestRun.pm,v
retrieving revision 1.166
diff -u -r1.166 TestRun.pm
---
+# _show_results() calls uses calls die() under a few
conditions,
calls uses calls ? :)
I swear something is wrong with me lately...
--Geoff
cross-posting to test-dev@, which is probably where we ought to discuss the
gory details...
Failed Test Stat Wstat Total Fail Failed List of Failed
at this point the test part of the perl-framework is
Use of uninitialized value in concatenation (.) or string at
/home/sctemme/asf/perl-framework/Apache-Test/lib/Apache/TestRequest.pm
The single request for /index.html is the framework's ping to see if
the server has started. It is not part of the errordoc tests, which
suggests that
blargh - cut and paste error. the subject should read Apache-Test-1.11.
--Geoff
Stas Bekman wrote:
Geoff, why did you make APACHE_TEST_NO_STICKY_PREFERENCES prevent from
saving autoconfig?
however it's done, I want an option wereby absolutely nothing sticky is ever
generated or used. the don't touch my system option was my goal, which
really isn't unreasonable.
so you're arguing that we should write out the sticky files, even if the
user doesn't ever want them interfering?
I'm not arguing at all. It's just when
APACHE_TEST_NO_STICKY_PREFERENCES=1 and no arguments passed, the logic
is broken. The program gets into a loop it can't break out of.
just some ideas.
Yeah, but we still have a problem to solve.
well, go ahead and remove the lack of save then, if you're certain that it
fixes the problem you're having. I don't really have the time at the moment
to implement an entire new mechanism. actually, I'd rather stay away from
Please show us the verbose trace:
t/TEST -trace=debug
including the part where you completed the interactive questions, and it
brought you back to interactive config again.
ok, the plan was to roll an official release this afternoon (as in now).
what's the feeling on this? release as is
The URL
http://perl.apache.org/~geoff/Apache-Test-1.11.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GE/GEOFF/Apache-Test-1.11.tar.gz
size: 116279 bytes
md5: 6a0e30ed99d84b683138b160e30ad474
--Geoff
Changes since 1.10:
if we fail to match the Apache revision (which is OK at
Rodent of Unusual Size wrote:
have_module() currently is rather terse when the problem with a
perl module is actually with something the module requires or uses.
here's a patch which will extract a little more info from $@ if it
can, and provide it as part of the message. helpful for
I think it's OK to add any extra logging in the verbose mode though
(when -verbose is passed) if you find it helpful as a developer. The
verbose mode is for developers and for when users have problems, so any
extra useful info is a goodness.
yeah, that's a good idea.
nevertheless, it
hi all.
we have been using Apache-Test to run our entire testing framework, which is
great - we can mix and match apache-related and non-apache related tests
under the same testing tree and it all works without a hitch.
the only problem is that when working on small testing units that don't
hi all...
as suggested by stas in a recent thread, it's about time we gave david
commit access to the perl-framework - he has been actively helping with the
project for as long as I can remember, from mac-specific stuff to lots of
great work on the (often thin) docs. and now he is working
Stas Bekman wrote:
David Wheeler wrote:
On Jun 23, 2004, at 9:02 AM, Stas Bekman wrote:
Now committed with a few minor tweaks, please test it since I don't
know how to test it. Thanks David.
Cool, thanks. What do you need to be able to feel comfortable/ready to
release it?
As I
+1
:)
+if ($self-{opts}-{'no-httpd'}) {
+warning skipping configuration: -no-httpd specified;
may be it's better to sayskipping httpd configuration?
sure, that's fine.
+return
please don't forget ; if } is on the next line.
oops :)
may be use -nohttpd, so
:
add -no-httpd runtime option to allow tests to run without configuring,
starting, or stopping Apache. this essentially provides a direct
Test::Harness interface through t/TEST, useful for running single tests
that do not depend on Apache. [Geoffrey Young]
Add support for Module::Build
Commenting out lines 669 and 1696 make it work fine. I remember having
this discussion a few months back but did not find a solution.
Apparently it is still an issue.
Yup, but it was an issue with previous A-T releases as well, so it's not
a showstopper. Someone who can reproduce this
David Wheeler wrote:
On Jun 25, 2004, at 8:31 AM, David Wheeler wrote:
blarg. a revised candidate is in the same place. sorry about that.
Thanks, I'll try it later today.
Works great for me! Only issue I'm seeing is that
Crequests_redirectable = 0 isn't working on one of my
Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
stas2004/06/27 11:46:03
Modified:perl-framework/Apache-Test/lib/Apache TestReportPerl.pm
perl-framework/Apache-Test Changes
Log:
Force projects that use Apache::TestReportPerl to implement
report_to() if
, useful for running single tests
that do not depend on Apache. [Geoffrey Young]
Add support for Module::Build, with a new module: Apache::TestMB (a
clone of Apache::TestMM for ExtUtils::MakeMaker). [David Wheeler
[EMAIL PROTECTED]]
switch the order of arguments in t_cmp() and t_is_equal() so
Original Message
Subject: FAIL Apache-Test-1.12 OpenBSD.i386-openbsd 3.5
Date: Mon, 28 Jun 2004 22:51:54 +0200 (CEST)
From: [EMAIL PROTECTED] (CPAN Tester. CPAN++ automate)
To: cpan-testers@perl.org
CC: [EMAIL PROTECTED]
This distribution has been tested as part of the
Original Message
Subject: [cpan #6800] Thread safety: work around perl sort bug
Date: Wed, 30 Jun 2004 05:42:03 -0400 (EDT)
From: Guest via RT [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: undisclosed-recipients:;
This message about Apache-Test was sent to you by guest
hi all...
the bug reporting skeleton has become so useful for me (and others) that I
have created two new skeletons:
http://perl.apache.org/~geoff/Apache-Test-skeleton-mp1.tar.gz
http://perl.apache.org/~geoff/Apache-Test-skeleton-mp2.tar.gz
these are essentially the same as the bug
Nice work, Geoff. May be they should live on CPAN, so one doesn't need
to remember where to grab them from? e.g. create an empty
Apache::Test::Skeleton::mod_perl(1|2) packages with versioning in those
tars and upload to CPAN?
that's an idea, but kind of a long name :) maybe just
[EMAIL PROTECTED] wrote:
theory 2004/07/09 13:01:26
Modified:perl-framework/Apache-Test Changes
perl-framework/Apache-Test/lib/Apache TestMB.pm
Log:
Be verbose in TestMB when verbosity is called for, but not otherwise.
can somebody please subscribe david to
The problem appears to be due to headers not being sent when using
Test::More. I found the code in Apache::Test which initializes a handler
when `plan $r, tests = 10` is called.
you can't use Test::More on the server side (that is, from a handler, such
as you have here). at least not with
William McKee wrote:
Hi Geoff,
Thanks for the info and the patch. I applied the patch without a problem
and then went to install the developer release of T::M. Dost my eyes
decieve me or does that say it was last updated on November 11, 2002?
That's a long release cycle.
indeed.
At
[Sun Jul 11 16:31:59 2004] [notice] Accept mutex: sysvsem (Default: sysvsem)
Warning: Use of require without parentheses is ambiguous at (eval 12)
line 1.
[Sun Jul 11 16:32:01 2004] [error] Undefined subroutine
TestApache::My::Bug::bug-tm::handler called.\n
[Sun Jul 11 16:32:01
I changed it to bugpm.pm (and changed the package name) and it worked fine.
Actually, changing it to bug_tm.pm works. I had forgotten to change the
package name when I retested :(. So hyphens in response tests are a bad
thing?
the limitation here is that perl package namespaces cannot
And may be this is a good idea for the A-T skeleton as well :)
indeed :)
actually, the bug reporting skeleton used t/My/Handler.pm, and I'll
certainly change that to t/lib not. the A-T module skeleton actually starts
with no supporting modules, since you would want to install the module
This makes the test fail against 2.0.50, but it's just a lack-of-feature
right, so OK if I half-revert this?
the last time I asked about this, the consensus was that the perl-framework
is expected to be for developer use only, expected to run (and in some cases
compile) successfully only on
ping
:)
--Geoff
Stas Bekman wrote:
Geoffrey Young wrote:
I'm not sure about the name choice. $(TEST_VERBOSE) and $(TEST_FILES)
are the same as other Test packages use. Do they have $TEST_EXTRA_ARGS
too? Otherwise we may better use some name specific to Apache-Test?
MakeMaker looks
Philippe M. Chiasson wrote:
Geoffrey Young wrote:
ping
:)
Must have fell off my radar. How is the following patch ?
+1
--Geoff
Using have_ macros for non-plan() usage should be avoided, since it
populates the SKIP messages array and if later the test is skipped, for
a different reason it'll misleadingly tell the user that LWP was also a
requirement for that test (which quite possibly could be what we want).
We need
OK, please let us know when and if you see it again.
I see that there were quite a few changes since the last A-T release,
any volunteers to wear the Release Manager cap and get a new version out?
I'll do it, once the need_* functions have been implemented (which I'll do
as well :)
--Geoff
hi all
ok, attached is a patch that implements the new need variants and alters the
old have variants. basically, all I did was a global rename of have to
need, then implement the have routines in terms of need with the AutoLoader.
I thought this made a bit more sense than redefining all of
I'd suggest to simply explain that there are have_ and need_ functions
at the beginning of that section that explains need_* ones. And one
should use need_* inside plan(), because of the skip messages. Otherwise
use have_*.
ok, done.
Please don't commit w/o the docs. Once it's committed,
:
the have() function was removed entirely - use need() instead.
[Geoffrey Young]
add need() and need_* variant functions (need_module(), need_apache(),
etc) for use specifically with plan() to decide whether or not a test
should run. have_* variants (have_module(), have_apache(), etc) are
now
hi all...
I just upgraded to libwww-perl 5.800 and found that a few POST tests started
failing where they didn't before, namely t/apache/post.t and t/http11/post.t.
I think the underlying problem is this change in HTTP::Message:
HTTP::Message will now allow an external 'content_ref'
to
hi all...
michael schwern is very close to releasing Test::More 0.49, which is the
first version of Test::More that we can use as the server-backend for
Apache::Test.
I would like to integrate the Test::More foo into A-T as soon as 0.49 comes
out. so, if you are interested in Test::More support
+Note that ITest::Builder 0.18_01, available in ITest::Simple
+version 0.48_01 on CPAN, is required to use this feature.
drop that, as 2 copies of the same thing in different places will go out
of sync at some point. check on the code level should be sufficient.
instead the error message
Stas Bekman wrote:
Do you also get these tests failing with the current httpd-2.0?
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/apache/limits.t 102 20.00% 7 9
I only
Stas Bekman wrote:
[EMAIL PROTECTED] wrote:
stas2004/08/08 23:19:16
Modified:perl-framework/Apache-Test/lib/Apache Test.pm
TestConfig.pm
TestRun.pm
Log:
another round of fixes of fixes
We are definitely not ready for the planned release.
Agreed. I'll try to reproduce it and resolve it. Sorry for the breakage.
no problem, that's part of the process.
Oh, yeah, I got it right away when trying to build mp2. Looking at it.
I think I've a good workaround for now. Please try again with the
current cvs. Still having a
obviously the release candidate from last week (or was it the week before)
has been cancelled due to some semi-major code revisions. are we in a
position where we can think about rolling a new candidate?
--Geoff
Joe Orton wrote:
Does the quote escaping really work in this function?
hmm, it doesn't look like it does. I think this was part of some work that
stas and ken were doing, though, and IIRC it was some win32 command line
thing. but I could be wrong.
It confuses emacs
font-lock mode which
and here is the optimized version of Geoff's one:
sub shell_ready_stas {
my $arg = shift;
$arg =~ s!\\?!\\!g;
return qq[$arg];
}
:)
Benchmark: timing 100 iterations of geoff, stas...
geoff: 64 wallclock secs (56.35 usr + 0.10 sys = 56.45 CPU) @
17714.79/s
David Wheeler wrote:
On Jul 31, 2004, at 5:04 PM, Stas Bekman wrote:
I guess losing the skip message by making need_ functions that
replace the existing have_ functions is okay. It's most important
that tests continue to pass...
They will.
Then I say we go with need.
I kind of
hi all...
in TestMM.pm we have this:
test_clean :
...
run_tests : test_clean
...
test :: pure_all run_tests test_clean
in a test suite with *lots* of files, test_clean takes forever. however, I
experience has shown me that test_clean is only really required when you
make
Are you sure that there will be no side effects?
I'm pretty sure. it's not like test_clean won't be called under normal
'make test' circumstances, it's just that now there would be a way around it
if the user thinks it is beneficial.
If yes, then +1
ok, cool. if things blow up then I'll
[EMAIL PROTECTED] wrote:
geoff 2004/09/15 16:55:31
Modified:perl-framework/Apache-Test Changes
perl-framework/Apache-Test/lib/Apache TestMM.pm
Log:
run_tests make target no longer invokes t/TEST -clean, making it
possible to save a few development cycles
+ Before:
Files=218, Tests=2512, 1032 wallclock secs (594.94 cusr + 431.33 csys
= 1026.27 CPU)
+ After:
Files=218, Tests=2512, 246 wallclock secs (196.69 cusr + 33.55 csys =
230.24 CPU)
gozer++, +1
whee!
gozer++
--Geoff
Stas Bekman wrote:
Geoffrey Young wrote:
hi all...
I've found it necessary to toggle single server mode when using
Apache-Test,
specifically for getting Devel::Cover to work with mod_perl 1.0
nicely. so,
I'd like to add an option for switching back to single server mode on
demand
When I unpack the tarball by hand, set
APACHE_TEST_HTTPD=/usr/sbin/httpdu, and run perl Makefile.PL; make;
make test, everything passes. This is true whether or not I am
executing the commands as root.
How can we programmatically figure out when to add the -u flag? If we
can't then we
Geoffrey Young wrote:
When I unpack the tarball by hand, set
APACHE_TEST_HTTPD=/usr/sbin/httpdu, and run perl Makefile.PL; make;
make test, everything passes. This is true whether or not I am
executing the commands as root.
How can we programmatically figure out when to add the -u flag? If we
+sub clean_files {
+return [
+qw(lib/Apache/TestConfigData.pm
+ .mypacklist
+ t/TEST
+ ),
+ ];
+}
[EMAIL PROTECTED] mod_perl-2.0]$ perl Makefile.PL
MP_APXS=/usr/local/apache2/bin/apxs
Reading Makefile.PL
Justin Erenkrantz wrote:
--On Wednesday, September 29, 2004 10:26 AM +0100 Joe Orton
[EMAIL PROTECTED] wrote:
Yup, the t_cmp arguments were flipped a while back.
FWIW, I think whomever flipped the t_cmp arguments but didn't flip the
included test cases at the same time needs a stern
hi all...
unless mod_perl 1.99_17 is imminent I'd like to roll Apache-Test 1.14 - now
that Devel::Cover works with mod_perl, 1.14 will be the first Apache-Test
release that has the ability to take advantage of Devel::Cover without
significant user modifications (namely due to the addition of
(httpd -X in Apache 1.X or
httpd -D ONE_PROCESS in 2.X) [Geoffrey Young]
In open_cmd, sanitize PATH instead of clearing it [Gozer]
Allow / \ and \\ path delimiters in SKIP file [Markus Wichitill
[EMAIL PROTECTED]]
Added an apxs query cache for improved test performance [Gozer]
run_tests make
argument, which will start the server
in single-server mode (httpd -X in Apache 1.X or
httpd -D ONE_PROCESS in 2.X) [Geoffrey Young]
In open_cmd, sanitize PATH instead of clearing it [Gozer]
Allow / \ and \\ path delimiters in SKIP file [Markus Wichitill
[EMAIL PROTECTED]]
Added an apxs query cache
[EMAIL PROTECTED] wrote:
jorton 2004/10/12 06:53:41
Modified:perl-framework/t/modules rewrite.t
perl-framework/t/conf extra.conf.in
Log:
Add test for RewriteRule [P] flag which is broken in HEAD
due to mod_proxy changes.
joe++
:)
--Geoff
@
if (my $custom_config_path = custom_config_path()) {
debug loading custom config data from: '$custom_config_path';
$custom_config_loaded++;
+($candidate) = $candidate=~/^(.*)/; # launder for -T
require $custom_config_path;
huh?
something
[EMAIL PROTECTED] wrote:
geoff 2004/10/28 07:33:56
Modified:perl-framework/Apache-Test Changes
perl-framework/Apache-Test/lib/Apache TestConfig.pm
Log:
revert last change to keep things compiling
sorry stas if you would have gotten to this quickly, but I
[EMAIL PROTECTED] wrote:
jorton 2004/10/25 06:04:14
Modified:perl-framework/t/conf extra.conf.in
Added: perl-framework/t/htdocs/security CAN-2004-0940.shtml
perl-framework/t/security CAN-2004-0940.t
Log:
Regression test for CAN-2004-0940, 1.3
If I had to guess, this borks anything but gmake. Test for that.
I had asked on #asf about this and somebody (I forget who) said that the
make manpage on minortaur (some bsd variant) supports ?= as well. from
looking at that it seems to be the manpage for pmake, which I guess is some
other
301 - 400 of 454 matches
Mail list logo
