jms-new-parser is part of v3.0 too, right?
I ran into issues with it:
It's doing some funky things w/ my command:
http://osl.iu.edu/~jjhursey/research/mtt/server/php/reporter.php?do_redir=7
It repeats the command string 5 times in some spots.
And should "network" and "runtime params" be blank
On Aug 24, 2007, at 9:46 AM, Ethan Mallove wrote:
jms-new-parser is part of v3.0 too, right?
I hope so. :-)
I ran into issues with it:
It's doing some funky things w/ my command:
http://osl.iu.edu/~jjhursey/research/mtt/server/php/reporter.php?
do_redir=7
I just filed a ticket about
Guys take a look at this email, and let me know if there is anything
missing before we sent it out.
The MTT development team has been working diligently on server side
optimizations over the past few months. This work involved major
changes to the database schema, web repo
Josh asked me to send some details on the "collectives performance
bakeoff" INI template file that its in the jms branch samples/ompi-
core-perf-testing.ini. Here's the scoop:
* As usual, this is a template. There are values that you will
need to fill in (e.g., the MTT database username/p
I volunteered to do this on the call today. Here's my thoughts on
tagging:
1. From the client, it would be nice to be able to specify a comma-
delimited list of tags at any phase. Tags would be inherited by
successive phases if not explicitly overridden. E.g., if you specify
a "foo" tag
