> > > - something else to look into, a recent bug has been introduced, if
> > > t/TEST -run=2 starts the server, when $SIG{INT} is caught it should
> > > stop the server but does not at the moment.
> >
> > I don't understand why would you want to do that. --run-tests is already a
> > non-standard execution, and when I debug it's quite nice to have the
> > server keep on running.
>
> it should be the same as running 't/TEST', if the server is not already
> running, it will be started for you, and should be stopped for you.
> if you want to keep the server running, start it yourself first with
> 't/TEST -start|debug'
>
> > In any case, I think that this is not related to the change I'm
> > introducing. Was it different beforehand?
>
> sort of, -run-tests didn't start the server before if it wasn't already
> running. but now that it does (which is fine), it should stop the server
> if it started it.
Oh, I understand. Will do.
> > Now, Doug, try --run-tests=20random, I've seen about 8% failure rate.
> > Since you should be able to reproduce problems in the random mode, I
> > introduce yet another option --seed. When you run in the random mode, the
> > seed is printed. So:
> > - is it ok to add this option?
> > - -s is taken :) what option name can I use?
> > - I can do --run-tests=N:mode:seed but then it gets too cumbersome
>
> how about just using an environment variable for the moment.
> hopefully the chances of needing to specify a seed will be rare.
let it be env var.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
