On Mon, Apr 18, 2011 at 10:50, Neels Hofmeyr <neels_at_elego.de> wrote:
> On Fri, 2011-04-15 at 03:18 -0400, Greg Stein wrote:
>> On Fri, Apr 15, 2011 at 00:13, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
>> > Just add them to public version control?
>> Already done. See tools/dev/benchmarks/suite1/
>> Looking at the scripts (along with a bit of work that I did), it seems
>> quite easy to incorporate the 'run' script directly into
>> 'benchmark.py', and (thus) make it more portable to Windows devs.
> Thanks, Greg, for your tweaks! I've just merged mine and am now using
> tools/dev/benchmarks/suite1/ instead of the elego repos.
> BTW, what's in the repos in suite1/ is now *exactly* what is run on the
> VM, no tweaks, just 'svn co'. (because I've added two ifs conditional to
> my username, for the svn-bins path and the email address...)
> Oh, but the scripts on the VM are not automatically updated, so if you
> tweaked and want to see the changes in the weekly mail, do ping me.
Will do. I'm going to fold much of 'run' into the .py script.
Eventually, 'run' should just be a simple way to type the N parameters
necessary to the benchmark script, which will then make it cake to
translate to a .BAT script for Windows.
> The benchmark will now run once a week on Monday morning and send
> results directly to dev@. Any objections?
Sounds great. If it starts to piss people off, then we can always
disable it. We could send it to notifications@, as an alternative.
Received on 2011-04-18 19:21:56 CEST