Hey Zubin!
On Sep 13, 2005, at 5:04 AM, Zubin Kika wrote:
I am a member of the Covalent QA team, and would like
tocontribute to httpd-test.
Welcome, welcome. The way this works is as follows: when you have a
suggestion for improvement, or a test that you would like to submit
to
On May 9, 2004, at 4:18 PM, Geoffrey Young wrote:
t/apache/errordoc.t 2 51214 14 100.00% 1-14
I added that test recently and it passes for me on fedora. can you try
$ t/TEST t/apache/errordoc.t -v
and send that along (along with any relevant error_log messages).
that all
tests
I recall hearing that SysV sems are notorious for that on
some platforms.
I'm thinking of having the SEM_UNDO flag while creating the semaphore (if
it's not already enabled)
APR's sysvsem IPC locks have undo enbaled.
There's one more thing I noticed (might be specific to HP-UX) : I saw
/usr/bin/perl -I/usr/lib/perl/5.6.1 -I/usr/share/perl/5.6.1 Makefile.PL
generating script ./t/htdocs/modules/rewrite/db.pl
APXS (/usr/sbin/apxs) query for SBINDIR failed
APXS (/usr/sbin/apxs) query for TARGET failed
APXS (/usr/sbin/apxs) query for SYSCONFDIR failed
This happens when you
where is config_vars.mk supposed to come from ?
Ought to be installed with Apache 2... in the build directory where libtool
sits, and a bunch of other build helpers.
S.
--
Covalent Technologies [EMAIL PROTECTED]
Engineering groupVoice: (415) 856 4214
303
So it can't be used to test remote servers now?
This is correct. Perl-framework and httpd are required to be on the same
host.
S.
--
Covalent Technologies [EMAIL PROTECTED]
Engineering groupVoice: (415) 856 4214
303 Second Street #375 South Fax:
All,
Months ago, Madhu posted a patch to put thread-safe locks around the Post
logging in mod_specweb99... here's an alternative using apr_global_mutex
locks:
Index: mod_specweb99.c
===
RCS file:
Hi all,
This patch fixes a problem that occurs when RSA SSL-C is used as back-end
for mod_ssl:
Index: t/conf/ssl/proxyssl.conf.in
===
RCS file:
/home/cvspublic/httpd-test/perl-framework/t/conf/ssl/proxyssl.conf.in,v
retrieving
on 7/10/03 18:00, Stas Bekman at [EMAIL PROTECTED] wrote:
Does this work?
else if ($redir) {
$RedirectOK = $redir;
}
It does. However, isn't this the same condition as in the top if clause?
Wouldn't you want to:
Index: Apache-Test/lib/Apache/TestRequest.pm
on 7/8/03 0:28, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
stas2003/07/08 00:28:28
Modified:perl-framework/Apache-Test/lib/Apache TestRequest.pm
Log:
Change the way the redirect_ok parameter works so that it affects only
_that call_ to the function. Afterward it should
on 7/10/03 12:56, Sander Temme at [EMAIL PROTECTED] wrote:
parameter to the request invocations in t/apache/acceptpathinfo.t. Neither
produces any result. Am I looking in the right place?
Breadcrumbing my way through Apache-Test/lib/Apache/TestRequest.pm by
liberally sprinkling print
on 5/19/03 23:01, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
This breaks on RH 8.0 and Solaris 7, both on perl 5.8.0, with the following
protest:
pxs /tmp/apache2/bin/apxs
Useless use of a constant in void context at
Apache-Test/lib/Apache/TestConfig.pm line 784.
Compilation failed in require
on 5/20/03 10:53, Sander Temme at [EMAIL PROTECTED] wrote:
This breaks on RH 8.0 and Solaris 7, both on perl 5.8.0, with the following
The following patch gets me back in the saddle, not only on Linux/Solaris
but also on Darwin 6.6:
Index: Apache-Test/lib/Apache/TestConfig.pm
Does anybody know if the mod_specweb99.c been 'blessed' by the SPEC
committee ?..I mean, have they acknowledged that the module acts in a SPEC
compliant manner?
As far as I am aware, the module has not been used for benchmarks submitted
to the SPEC organization. That is the moment any code
Is this against the spec or something ?.
Which spec? If you are referring to either the SPECWeb99 run rules or to
RFC2616, neither of them dictate which syscalls you use.
IIRC, the SPECWeb99 run rules just say that you have to treat ad expiration
correctly.
S.
--
Covalent Technologies
If you're worried about the overhead of calling pthread_lock and
pthread_unlock under the covers when it's not needed (like on the prefork MPM)
then I would say that's not a big problem. Locking mutexes that are not
contended for can be quite cheap, and often those calls do not even translate
I noticed that there were some places where u_int32_t is being used instead
of apr_uint32_t. Is it purposefully done OR is it one of those Oh, the apr
interface changed stuff ?.
Anyways, I've included a patch that atleast gets the module to compile
against 2.0.43. Pl. let me know if it's
Also - hack the conf to do short runs first !
Oh yeah, excellent point. That's the SPEC rc file. Look for *_TIME,
ITERATIONS, and SIMULTANEOUS_CONNECTIONS.
My rc files usually have trial (short) values for *_TIME and a single
iteration. You can force all those in line for a compliant run
When trying to run vanilla 't/TEST' on AIX, with httpd-2.0 HEAD,
I'm getting a
waiting for server to start: 00:00
server has died with status 255 (please examine t/logs/error_log)
Exactly the same deal on:
Darwin 5.2
FreeBSD 4.4
S.
--
Covalent Technologies
19 matches
Mail list logo
