Re: Is there a way to disable the ANSI?
if you have the fix, just send along the patch and i can commit for you. wait...did you already do that once? -j On Thu, Aug 30, 2001 at 11:55:26PM +0100, Gary Benson wrote: + + On Thu, 30 Aug 2001, Ian Holsman wrote: + + > I'm trying to get a nightly test going, + > (nearly done) + + If you are running it from cron then the mod_env tests will fail. Don't + worry; when my commit access works I'll commit a fix... + + Gary + + [ Gary Benson, Red Hat Europe ][ [EMAIL PROTECTED] ][ GnuPG 60E8793A ] +
Re: Is there a way to disable the ANSI?
On Thu, 30 Aug 2001, Ian Holsman wrote: > I'm trying to get a nightly test going, > (nearly done) > > and the escape codes look ugly. > anyway of disabling them?? what is 'the ANSI'? and 'escape codes'?
Re: Anyone know what this means?
Brian added you to the avail file earlier today, so you can commit now. Roy On Thu, Aug 30, 2001 at 11:58:59AM -0700, Aaron Bannert wrote: > CVS has an extra layer of access permissions that are preventing you from > doing a commit. You need to get added to the accel file for httpd-test. > (I don't know who can do this for you, sorry). > > -aaron > > > On Thu, Aug 30, 2001 at 07:34:56PM +0100, Gary Benson wrote: > > > > Access denied: Insufficient Karma > > (gbenson|httpd-test/perl-framework/t/php)cvs server: Pre-commit check > > failed > > Access denied: Insufficient Karma > > (gbenson|httpd-test/perl-framework/t/htdocs/php) > > cvs server: Pre-commit check failed > > cvs [server aborted]: correct above errors first! > > cvs commit: saving log message in /tmp/cvsS0ABZQ > >
Re: Is there a way to disable the ANSI?
On Thu, 30 Aug 2001, Ian Holsman wrote: > I'm trying to get a nightly test going, > (nearly done) If you are running it from cron then the mod_env tests will fail. Don't worry; when my commit access works I'll commit a fix... Gary [ Gary Benson, Red Hat Europe ][ [EMAIL PROTECTED] ][ GnuPG 60E8793A ]
Is there a way to disable the ANSI?
I'm trying to get a nightly test going, (nearly done) and the escape codes look ugly. anyway of disabling them?? ..Ian
Re: Anyone know what this means?
CVS has an extra layer of access permissions that are preventing you from doing a commit. You need to get added to the accel file for httpd-test. (I don't know who can do this for you, sorry). -aaron On Thu, Aug 30, 2001 at 07:34:56PM +0100, Gary Benson wrote: > > Access denied: Insufficient Karma > (gbenson|httpd-test/perl-framework/t/php)cvs server: Pre-commit check > failed > Access denied: Insufficient Karma > (gbenson|httpd-test/perl-framework/t/htdocs/php) > cvs server: Pre-commit check failed > cvs [server aborted]: correct above errors first! > cvs commit: saving log message in /tmp/cvsS0ABZQ >
Anyone know what this means?
Access denied: Insufficient Karma (gbenson|httpd-test/perl-framework/t/php)cvs server: Pre-commit check failed Access denied: Insufficient Karma (gbenson|httpd-test/perl-framework/t/htdocs/php) cvs server: Pre-commit check failed cvs [server aborted]: correct above errors first! cvs commit: saving log message in /tmp/cvsS0ABZQ
Re: running subtests
that rules.
Re: running subtests
On Thu, 30 Aug 2001, Doug MacEachern wrote: > so for example, you can now do this: whoops, left out this part: % ./t/TEST -v t/modules/env.t 3 5 > modules/env1..5 > ok 1 # skip skipping this subtest > ok 2 # skip skipping this subtest > set: EXPECT ->mod_env test environment variable<- ACTUAL ->mod_env test > environment variable<- > ok 3 > ok 4 # skip skipping this subtest > unset: EXPECT ->(none)<- ACTUAL ->(none)<- > ok 5 > ok, 3/5 skipped: skipping this subtest > All tests successful. > Files=1, Tests=5, 2 wallclock secs ( 1.09 cusr + 0.07 csys = 1.16 CPU) >
running subtests
it is now possible to write .t tests in such a way that only selected
tests will be run. the .t's simply need to switch from using 'ok ...'
to 'sok { ... }'. where the argument to sok is a subroutine reference
who's return value will be passed to 'ok'. if subtests are specified
only those will be run/passed to ok, the rest will be skipped.
so for example, you can now do this:
modules/env1..5
ok 1 # skip skipping this subtest
ok 2 # skip skipping this subtest
set: EXPECT ->mod_env test environment variable<- ACTUAL ->mod_env test
environment variable<-
ok 3
ok 4 # skip skipping this subtest
unset: EXPECT ->(none)<- ACTUAL ->(none)<-
ok 5
ok, 3/5 skipped: skipping this subtest
All tests successful.
Files=1, Tests=5, 2 wallclock secs ( 1.09 cusr + 0.07 csys = 1.16 CPU)
Re: File::Tail
On Thu, Aug 30, 2001 at 09:58:19AM -0700, Doug MacEachern wrote: + i'd rather just change the test to write to its own file rather than + error_log, if we can prevent a dependency on File::Tail. oh yeah. this reminds me. i thought about doing something like this but dont know enough about php to quickly know whats possible and whats not. the test is testing php's register_shutdown_function. so, the function we register doesnt HAVE to write to a file, it can do anything that can be verified after the connection is closed. so if anyone has an idea about something easier to verify than writing to a file, we can do that. ideas? -j
Re: File::Tail
On Thu, 30 Aug 2001, Doug MacEachern wrote: > On Thu, 30 Aug 2001, Gary Benson wrote: > > > > > Hi all, > > > > I've got three problems which I could resolve easily if I were able to > > call on the File::Tail package (which tails files would you believe). These > > being: > > > > * php/func5.t fails if the log entry doesn't get written straight > >to the disk > > * php/func5.t will pass on the first "foo() has been called" message, so > >we could have false passes. > > i'd rather just change the test to write to its own file rather than > error_log, if we can prevent a dependency on File::Tail. What a fine idea. Consider it (about to be) done...
Re: File::Tail
On Thu, 30 Aug 2001, Gary Benson wrote: > > Hi all, > > I've got three problems which I could resolve easily if I were able to > call on the File::Tail package (which tails files would you believe). These > being: > > * php/func5.t fails if the log entry doesn't get written straight >to the disk > * php/func5.t will pass on the first "foo() has been called" message, so >we could have false passes. i'd rather just change the test to write to its own file rather than error_log, if we can prevent a dependency on File::Tail. > * TestServer::start sometimes fails on slow machines we can increase the sleep time waiting for the server to start if that helps. > What I want to know is if anyone has a problem with me using this package, > and whether or not we could add it to the httpd-test-bundle. feel free to use any cpan module, just try not to make them requirements for running tests (i.e. skip if module is not available). we really need a script to autogenerate the test-bundle.tar.gz: http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=99764631217375&w=2
Re: File::Tail
i have no problem with this. i also thought about the false passes for that test, but have been too busy with other test modules to think much about how to fix it. -j On Thu, Aug 30, 2001 at 05:07:02PM +0100, Gary Benson wrote: + + Hi all, + + I've got three problems which I could resolve easily if I were able to + call on the File::Tail package (which tails files would you believe). These + being: + + * php/func5.t fails if the log entry doesn't get written straight +to the disk + * php/func5.t will pass on the first "foo() has been called" message, so +we could have false passes. + * TestServer::start sometimes fails on slow machines + + What I want to know is if anyone has a problem with me using this package, + and whether or not we could add it to the httpd-test-bundle. + + Comments? + Gary + + [ Gary Benson, Red Hat Europe ][ [EMAIL PROTECTED] ][ GnuPG 60E8793A ] +
File::Tail
Hi all, I've got three problems which I could resolve easily if I were able to call on the File::Tail package (which tails files would you believe). These being: * php/func5.t fails if the log entry doesn't get written straight to the disk * php/func5.t will pass on the first "foo() has been called" message, so we could have false passes. * TestServer::start sometimes fails on slow machines What I want to know is if anyone has a problem with me using this package, and whether or not we could add it to the httpd-test-bundle. Comments? Gary [ Gary Benson, Red Hat Europe ][ [EMAIL PROTECTED] ][ GnuPG 60E8793A ]
Re: Core dump scan breaks exit() status
> > > I see, try this patch (untested):
> >
> > I didn't realize that END {} is a block already :) here is a simpler patch
> > (still untested):
> >
> > 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.41
> > diff -u -r1.41 TestRun.pm
> > --- Apache-Test/lib/Apache/TestRun.pm 2001/08/27 05:55:17 1.41
> > +++ Apache-Test/lib/Apache/TestRun.pm 2001/08/29 15:49:48
> > @@ -221,6 +221,7 @@
> > #always run, a subclass might not want that
> >
> > eval "END {
> > + local $?; # preserve the exit status
> > eval {
> > Apache::TestRun->new(test_config =>
> > Apache::TestConfig->thaw)->scan;
>
> Stas, thanks, that worked a treat. May I request that you commit it?
committed.
_
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://localhost/ http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
