>> On Oct 28, 2008, at 2:06 AM, Mike Dubman wrote:
>> > Hey Jeff,
>> > I have no svn permissions to commit. Can you please provide me with
>> > one? (login: miked)
>> > Thanks
Please suggest the proper way to handle the following:
Is there any way to run "test run" section with a list of "mpi_details"
Or how to execute specific "Test run" section against specific "mpi_details"
section, where "mpi_details" can have many different scenarios of
Thanks for the tip, nice way to achieve multi-scenarios for single
On Mon, Nov 3, 2008 at 5:45 PM, Ethan Mallove <ethan.mall...@sun.com> wrote:
> On Mon, Nov/03/2008 09:34:07AM, Mike Dubman wrote:
> >Hello Guys,
Ethan Mallove wrote:
> On Mon, Nov/03/2008 09:34:07AM, Mike Dubman wrote:
>>> Hello Guys,
>>> Please suggest the proper way to handle the following:
>>> Is there any way to run "test run" section with a list
yep. it works. I thought that "exec" for mpirun will be executed once with
all @mca@ params passed to it.
On Tue, Nov 4, 2008 at 2:08 PM, Jeff Squyres <jsquy...@cisco.com> wrote:
> On Nov 4, 2008, at 1:18 AM, Mike Dubman wrote:
> Do you mean that y
I`ll help, lead us master.
On Tue, Mar 10, 2009 at 6:01 PM, Josh Hursey wrote:
> Yeah I have some time to dedicate do this. We should talk about a couple of
> specific topics to propose from this list we posted on the wiki.
> I can start digging in later this
because the results are rendered in chunks during reporting phase. (100
pieces every flush)
This caused same benchmark line to appear more then once in the final
You can configure the reporter to issue results not by number, but for same
benchmark at once:
put this in the ini file:
I think we can switch to desired framework (datastore+mapreduce) gradually
in the background:
Here is a short battle plan:
1. create datastore (google`s or similar)
2. design datastore layout (what to keep, how to keep, objects & attributes)
3. create cmd line tool to submit results into
Thanks for info, will refactor it.
*HPL* is a software package that solves a (random) dense linear system in
double precision (64 bits) arithmetic on distributed-memory computers. It
can thus be regarded as a portable as well as freely
I`m not sure if we should preserve current DB schema, from one simple reason
- datastore is an object oriented storage and have different rules and
techniques then rdbms.
The basic storage unit in the datastore is an object which can be saved,
loaded and queried.
(hadoop is based on
week and likely won't be able to look
> into this stuff -- can you guys post a proposal and we can dive into it from
> that angle?
> On Mar 22, 2009, at 6:48 AM, Mike Dubman wrote:
> Hello guys,
>> I`m not sure if we should preserve current DB schema, from
I have played a bit with google datastore and here is a proposal for mtt DB
infra and some accompanying tools for submission and querying:
1. Scope and requirements
a. provide storage services for storing test results generated by mtt.
Storage services will be
Please comment on the proposed object model and flows. We will have 1-2 ppl
working on this in a 2-3w. Till that moment I would like to finalize the
scope and flows.
On Mon, Apr 6, 2009 at 4:54 PM, Mike Dubman <mike.o...@gmail.com> wrote:
> Hello Guys,
resending original post with attachment (mtt_datastore.tbz). it is sample
google appengine API application. It contains models.py with object model
proposal and script with some examples of object model use-cases and flows.
-- Forwarded message --
From: Mike Dubman <mik
On Mon, Apr 13, 2009 at 5:44 PM, Ethan Mallove wrote:
> Will this translate to something like
> lib/MTT/Reporter/GoogleDatabase.pm? If we are to move away from the
> current MTT Postgres database, we want to be able to submit results to
> both the current
On Tue, Apr 14, 2009 at 5:04 PM, Jeff Squyres <jsquy...@cisco.com> wrote:
> On Apr 13, 2009, at 2:08 PM, Mike Dubman wrote:
> Hello Ethan,
> Sorry for joining the discussion late... I was on travel last week and that
> always makes me waaay behind on my I
On Tue, Apr 14, 2009 at 11:50 PM, Ethan Mallove <ethan.mall...@sun.com>wrote:
> On Tue, Apr/14/2009 09:27:14PM, Mike Dubman wrote:
> >On Tue, Apr 14, 2009 at 5:04 PM, Jeff Squyres <jsquy...@cisco.com>
> > On Apr 13, 2009, at 2:08 PM, Mik
On Wed, Apr 15, 2009 at 3:51 AM, Jeff Squyres <jsquy...@cisco.com> wrote:
> On Apr 14, 2009, at 2:27 PM, Mike Dubman wrote:
> Ah, good point (python/java not perl). But I think that
>> lib/MTT/Reporter/GoogleDataStore.pm could still be a good thing -- we have
On Wed, Apr 15, 2009 at 5:23 PM, Jeff Squyres <jsquy...@cisco.com> wrote:
> On Apr 15, 2009, at 9:14 AM, Mike Dubman wrote:
> Hmm. Ok, so you're saying that we define a "phase object" (for each
>> phase) with all the fields that we expect to have, but if we n
On Wed, Apr 15, 2009 at 8:50 PM, Jeff Squyres <jsquy...@cisco.com> wrote:
> On Apr 15, 2009, at 1:45 PM, Mike Dubman wrote:
> yep. correct. We can define only static attributes (which we know for sure
>> should present in every object of given type and leave phase s
I will prepare ppt with summary of what were discussed and agreed,
milestones, open questions and other thoughts.
On Thu, Apr 16, 2009 at 2:07 PM, Jeff Squyres wrote:
> Ok, I think we converged on a time: 9am US Eastern / 4pm Israel next
> Thuesday, April 23.
t; (no need to be formal; if slides help, great, otherwise don't make slides
> just because we have webex available)
> On Apr 16, 2009, at 9:50 AM, Mike Dubman wrote:
> I will prepare ppt with summary of what were discussed and agreed,
>> milestones, open questions and
This code acts as a pre-processor during loading of ini file into mtt.
It replaces builtin vars %VAR% with their values, for example:
[Test run: trivial]
%INI_SECTION_NAME% get replaced with real value. (trivial)
it is useful in the following
It seems argv is participating in the following scenarios:
1. argv should be defined in mtt.ini for every single [Test Run] section
2. Currently, _argv() is returing un-evaluated argv`s value
3. _argv() is usually part of "exec=" parameter line of [MPI Details],
which is evaluated
On Fri, Sep 25, 2009 at 10:08 PM, Jeff Squyres <jsquy...@cisco.com> wrote:
> On Sep 24, 2009, at 12:46 PM, Mike Dubman wrote:
> Im not familiar with :\n semantics, how does it force Bourne shell and
>> what it actually does :)? (seems like leftovers from 1960)
it seems it can be retired. executable() covers more cases.
shell() can be the alias of executable() for backwards compatibility.
Also, DoCommand::CmdScript should be changed to DoCommand::Cmd inside
executable() to really cover more cases.
On Tue, Sep 29, 2009 at 8:35 PM, Ethan
mtt fails on sles11up2 with perl version 5.10.0 but works on other distros
as a charm.
The same minimalistic ini file which works on other distro`s fails on sles
>> Test Run [osu]
>> Running with [open mpi] / [1.3.3] / [openmpi]
Using MPI Details [open mpi] with MPI
Also, there is an MTT option to select Google Datastore as a storage backend
for mtt results.
- your data is stored in the Google`s cloud
- You can access your data from scripts
- You can create a custom UI for you data visualization
- You can use Google`s default datastore querying
Do you know if there is mtt option to stop mtt execution if job`s failure
ratio succeeds specified value, something like:
Also, are there any ini files examples/successes of how to use mtt with
non-MPI based applications?
0 PM, Jeff Squyres <jsquy...@cisco.com> wrote:
> Mike --
> MongoDB is a NoSQL thingy, right?
> Can you describe this plugin a bit? Do you guys have some kind of
> reporter for MongoDB?
> On Aug 1, 2012, at 5:46 AM, <svn-commit-mai...@open-mpi.org> wrote:
from shebang. Somehow and sometimes it can become zombie.
exec =< -Original Message-
> From: Jeff Squyres (jsquyres) [mailto:jsquy...@cisco.com<jsquy...@cisco.com>
> Sent: Sunday, February 24, 2013 13:10
> To: <mtt-de...@open-mpi.org
/var/run is only writable to root, but script uses it explicitly.
maybe it is worse to add fallback if non-root user starts mtt-relay.
On Mon, Sep 30, 2013 at 2:08 PM, Christoph Niethammer wrote:
> As on many systems init scripts and the handling of services is
ould be a
> LOT of output.
> On Apr 5, 2014, at 7:27 PM, <svn-commit-mai...@open-mpi.org> wrote:
> > Author: miked (Mike Dubman)
> > Date: 2014-04-05 19:27:28 EDT (Sat, 05 Apr 2014)
> > New Revision: 1637
> > URL: https://svn.open-mpi.org/trac/mtt/chan
ry* verbose, and is generally only
> useful when something goes wrong.
> I run Cisco's automated MTT with only --verbose.
> On Apr 7, 2014, at 6:35 PM, Mike Dubman <mi...@dev.mellanox.co.il> wrote:
> > ohh.. it is just flooding the log with same data for every test
ths, at a minimum.
> On Jun 23, 2014, at 4:37 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote:
> > this commit does more harm then good.
> > we experience following:
> > - some child processes still running after timeout a
> On Jun 23, 2014, at 7:47 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote:
> > after patch, it killed child processes but kept mpirun ... itself.
> What does that mean -- are you saying that mpirun is still running? Was
Mail list logo