Looks perfect! ;)

On Jan 23, 2011, at 4:27 PM, Fred Moyer wrote:

> On Sun, Jan 23, 2011 at 10:52 AM, Jim Jagielski <j...@jagunet.com> wrote:
>> 
>> I'll try SMOKE... I basically use times simply to run the same
>> test over and over. For example, when people said that the proxy
>> changes caused the rewrite tests to occasionally fail, a
>> 
>>        t/TEST -times=100 t/modules/rewrite
>> 
>> was a good way to try to recreate that...
> 
> I've made a number of changes which will hopefully fill the needs
> here.  This solution may not be able to go through tests as rapid fire
> as previously, but should be able to do 100 times in less than 2
> hours.  See the output below fo the syntax I used.  Feedback welcome.
> 
> New Revision: 1062529
> URL: http://svn.apache.org/viewvc?rev=1062529&view=rev
> 
> So -times=X in ./t/TEST has been removed, but is now in t/SMOKE.
> t/SMOKE also does away with the concept of iterations, and for random
> ordering it creates a new seed before each 'time'.
> 
> phred@pooky ~/dev/svn/httpd/test/framework/trunk $ time t/SMOKE
> -times=10 -verbose t/modules/rewrite
> Using random number seed: 3285025243 (autogenerated)
> Report file: 
> /Users/phred/dev/svn/httpd/test/framework/trunk/smoke-report-Sun_Jan_23_13-23-07_2011.txt
> 
> ------------------------------------------------------------
> [001-00-10] running all tests
> Using random number seed: 3285025243 (autogenerated)
> t/modules/rewrite..ok
> 
> ------------------------------------------------------------
> [002-00-10] running all tests
> Using random number seed: 3285025188 (autogenerated)
> t/modules/rewrite..ok
> 
> real    1m26.050s
> 
> ...
> 
> ========================= Summary ==========================
> Completion               : Completed
> Status                   : +++ OK +++
> Tests run                : 10
> Iterations (random) made : 10
> ------------------------------------------------------------
> --- Started at: Sun Jan 23 13:23:07 2011 ---
> --- Ended   at: Sun Jan 23 13:24:32 2011 ---
> ------------------------------------------------------------
> 

Reply via email to