--- Matt Diephouse <[EMAIL PROTECTED]>
wrote:

> # New Ticket Created by  Matt Diephouse 
> # Please include the string:  [perl #33642]
> # in the subject line of all future correspondence
> about this issue. 
> # <URL:
>
http://rt.perl.org:80/rt3/Ticket/Display.html?id=33642
> >
> 
> 
> parrotbench.pl currently cd's into the benchmark
> directory before 
> running the benchmarks. This patch changes the
> program to run them from 
> its own directory. I've done this because many of
> the benchmarks need 
> to be run from the root parrot directory. This has
> been causing some 
> problems for the performance stats.

This is because there is no "smart" find yet for
.include statements.  I have been out of the loop
since  late November and will likely continue to be. 
I was hoping making the benchmarks part of the test
suite my prompt some one with tuits to fix this.  It
may be that the fix itself is a design decision and
there is as of yet no ruling.

> 
> Joshua Gatcomb should comment on whether or not this
> should be applied. 

Apply away.  I have held off making any modifications
waiting on another design decision.  Leo opened up a
ticket on this script because it used a non-core Perl
module.  I listed a dozen or so other non-core Perl
dependencies in other scripts and asked what was the
proper way to handle it with no definitive answer.

Personally, my feeling is that anything not required
to configure, compile, install, or run Parrot should
be allowed to have non-core dependencies as a
usr/contrib.

You can run the benchmarks without the script - it
just makes automating them and getting pretty output
easier.

> Either way, it'll be used for a local copy of
> parrotbench.pl on the 
> stats server.

Thanks! I haven't looked at the stats for a month - I
hope we are doing great.

> 
> --
> matt diephouse
> http://matt.diephouse.com


Cheers
Joshua Gatcomb
a.k.a. Limbic~Region


                
__________________________________ 
Do you Yahoo!? 
Send a seasonal email greeting and help others. Do good. 
http://celebrity.mail.yahoo.com

Reply via email to