Hello guys,
Please consider applying attached mtt patch to allow following features:
1. Support for centos5
2. Send single, digested email report for all completed tests (similar
to text file summary file)
3. Provide basic statistics in the digested email about completed test
s
> maintained by Brian Finley at Argonne National Labs).
>
>
>
> On Oct 26, 2008, at 10:14 AM, Mike Dubman wrote:
>
>
>> Hello guys,
>>
>> Please consider applying attached mtt patch to allow following features:
>>
>>• Support for centos5
ic enough that it should
> work for any lsb_release-capable machine (to include Centos 5).
>
> I pulled that down into the MTT trunk; Mike, could you verify that it works
> for you?
>
>
>
> On Oct 28, 2008, at 8:30 AM, Jeff Squyres (jsquyres) wrote:
>
> Done!
>>
>
Hello Guys,
Please suggest the proper way to handle the following:
Is there any way to run "test run" section with a list of "mpi_details"
sections?
Or how to execute specific "Test run" section against specific "mpi_details"
section, where "mpi_details" can have many different scenarios of comma
Ethan,
Thanks for the tip, nice way to achieve multi-scenarios for single
mpi_details section.
Mike.
On Mon, Nov 3, 2008 at 5:45 PM, Ethan Mallove wrote:
> On Mon, Nov/03/2008 09:34:07AM, Mike Dubman wrote:
> >Hello Guys,
> >
> >Please suggest the proper way to
han 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.
Thanks again.
Mike
On Tue, Nov 4, 2008 at 2:08 PM, Jeff Squyres wrote:
> On Nov 4, 2008, at 1:18 AM, Mike Dubman wrote:
>
> Do you mean that you have a huge "
Hello guys,
I`m looking for a way having automatic regression report at the end of mtt
run which include graph+table for bw/lat/2way-bw for this specific run as
well as for previous runs on the same configuration.
The way we are doing it, is generating dynamic query for MTT test reporter
at the
Hello guys,
Using MapReduce or any other in-memory DB techque sounds cool and should
provide fast access to all perfomance data.
Here is a wiki page with some ideas for mtt addons:
https://svn.open-mpi.org/trac/mtt/wiki/MttNewFeaturesIdeas
regards
Mike
On Wed, Feb 25, 2009 at 6:47 PM, Jeff Squ
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 evening/tomorrow morning.
>
> -- J
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
report.
You can configure the reporter to issue results not by number, but for same
benchmark at once:
put this in the ini file:
[MTT]
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 datastor
Hello Eithan,
Thanks for info, will refactor it.
from http://www.netlib.org/benchmark/hpl/
...
*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 a
Hello guys,
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 th
ly 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 one simple
&
Hello Guys,
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 i
Hello Guys,
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.
Thanks
Mike.
On Mon, Apr 6, 2009 at 4:54 PM, Mike Dubman wrote:
> Hello Guys,
>
> I have played a bit wi
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
List-Post: mtt
Hello Ethan,
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 MTT database and the new
On Tue, Apr 14, 2009 at 5:04 PM, Jeff Squyres 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 INBOX. :-(
>
> On Mon,
On Tue, Apr 14, 2009 at 11:50 PM, Ethan Mallove wrote:
> On Tue, Apr/14/2009 09:27:14PM, Mike Dubman wrote:
> >On Tue, Apr 14, 2009 at 5:04 PM, Jeff Squyres
> wrote:
> >
> > On Apr 13, 2009, at 2:08 PM, Mike Dubman wrote:
> >
> >Hello Ethan
On Wed, Apr 15, 2009 at 3:51 AM, Jeff Squyres 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
>> invested a lot of time/ef
On Wed, Apr 15, 2009 at 5:23 PM, Jeff Squyres 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 need to, we can
>>
On Wed, Apr 15, 2009 at 8:50 PM, Jeff Squyres 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 specific
>> attributes to st
I will prepare ppt with summary of what were discussed and agreed,
milestones, open questions and other thoughts.
regards
Mike
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.
>
> I'll send the webe
; 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 other thoughts
Hey Jeff,
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]
my_sect_name=%INI_SECTION_NAME%
...
%INI_SECTION_NAME% get replaced with real value. (trivial)
it is useful in the following
ction name of its
location inside mtt ini file.
I moved %INI_SECTON_NAME% to @VAR@ syntax and put it into
InsertINIPredefines()
Thanks for comment.
regards
Mike
On Tue, Aug 11, 2009 at 5:33 PM, Ethan Mallove wrote:
> On Tue, Aug/11/2009 02:53:50PM, Mike Dubman wrote:
> >Hey Jeff,
&
Hey Eytan,
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, &test_argv() is returing un-evaluated argv`s value
3. &test_argv() is usually part of "exec=" parameter line of [MPI Details],
which is eva
yep
On Wed, Sep 9, 2009 at 6:35 PM, Ethan Mallove wrote:
> On Wed, Sep/09/2009 10:30:44AM, Mike Dubman wrote:
> >Hey Eytan,
> >
> >It seems argv is participating in the following scenarios:
> >
> >1. argv should be defined in mtt.ini for every sin
Hey Jeff,
On Thu, Sep 24, 2009 at 4:02 PM, Jeff Squyres wrote:
> The DoCommand.pm sub added ":\n" to the beginning to force the Bourne shell
> interpreter. This is necessary for some cases where an interpreter is not
> otherwise specified.
>
Im not familiar with :\n semantics, how does it forc
On Fri, Sep 25, 2009 at 10:08 PM, Jeff Squyres 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)
>>
>
> Yes, it m
Hello guys and gals,
We have completed development and testing of Google DataStore support in MTT
and are glad to submit it for community tests.
New Files:
The following new files were added to support GDS inside MTT:
1. client/bquery.pl
Perl-based GDS client, provides basic DB q
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.
regards
Mike
On Tue, Sep 29, 2009 at 8:35 PM, Ethan Mal
Hello guys,
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
with error:
>> Test Run [osu]
>> Running with [open mpi] / [1.3.3] / [openmpi]
Using MPI Details [open mpi] with MPI I
On Fri, Feb 12, 2010 at 6:44 PM, Jeff Squyres wrote:
> > > 2. In reading through the Google Appengine docs, the GDS stuff looks
> like
> > we mainly can access the data through GQL. I don't see any mention of
> doing
> > map/reduce kinds of computations (Ethan and I were talking on the phone
> >
Hi,
Also, there is an MTT option to select Google Datastore as a storage backend
for mtt results.
Pro:
- 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
Hi,
it is c-style *switch* replacement, to simplify statements like this:
transport = &if (&eq('@cycle@', '1'), '@btl_openib@' ,\
&if (&eq('@cycle@', '2'), '@btl_openib@',\
&if (&eq('@cycle@', '3'), '@btl_eth10g@',\
&if (&e
Hi,
Do you know if there is mtt option to stop mtt execution if job`s failure
ratio succeeds specified value, something like:
[mtt]
stop_on_test_failures=1%
Also, are there any ini files examples/successes of how to use mtt with
non-MPI based applications?
Thanks
Mike
:Values::SKIPPED} = Value($ini, $section,
"break_threshold_skipped");
but it seems like "break rules" are available per single test section
instead of whole mtt session.
Regards
Mike
On Tue, Jan 4, 2011 at 3:42 PM, Joshua Hursey wrote:
>
> On Jan 4, 2011, at 8:04 AM, Jef
;"
> EOT
>
>
> [Test run: iu_ft_cr]
> include_section = Defaults Test run
>
> test_build = iu_ft_cr
> timeout = &max(240, &multiply(30, &test_np()))
> pass = &and(&test_wifexited(), &eq(&test_wexitstatus(), 0))
> np = &env_max_proc
Hi guys,
Mtt`s funclets do not work on new perl version which is shipped with RHEL6,
SLES11.
The simple reproduce is:
np=&step()
It seems new perl does not like eval way used in mtt.
any thoughts?
10x
M
This commit fixes the problem:
https://svn.open-mpi.org/trac/mtt/changeset/1383
On Mon, Jan 24, 2011 at 7:54 PM, Ethan Mallove wrote:
> On Fri, Jan/21/2011 10:51:41AM, Mike Dubman wrote:
> >Hi guys,
> >Mtt`s funclets do not work on new perl version which is shipped wi
Hi guys,
There is a race condition in SCM, Mercurial module when used from MPI GET
phase:
- scm_post_copy hook can be started before MPI GET completed copy of fetched
tree into install location.
- This leads to mtt failure, because post_copy starts too early (tree was
not copied yet) and fails.
-
opytree finished copying
On Fri, Feb 18, 2011 at 12:23 AM, Jeff Squyres wrote:
> On Feb 10, 2011, at 2:36 PM, Mike Dubman wrote:
>
> > There is a race condition in SCM, Mercurial module when used from MPI GET
> phase:
> >
> > - scm_post_copy hook can be started b
ytree?
>
> I don't think that I have used the Mercurial SCM module before -- I believe
> Ethan added that. Ethan -- does SCM/Mercurial work well for you?
>
>
>
> On Feb 18, 2011, at 2:06 AM, Mike Dubman wrote:
>
> >
> > 1. post_copy fails because doe
done
credit goes to Valentin as a creator of this feature!
On Wed, Jan 25, 2012 at 3:11 PM, Jeff Squyres wrote:
> Yummy -- thanks Mike!
>
> Can you add this field (and any others you have added) to the wiki?
>
>https://svn.open-mpi.org/trac/mtt/wiki/MTTINIFileFields
>
> This is our *only* do
already there!
:)
On Fri, Mar 2, 2012 at 6:36 PM, Jeffrey Squyres wrote:
> Sweet!
>
> Can you document this on the wiki in the listing of all the INI fields?
>
>
> On Mar 2, 2012, at 10:27 AM, mi...@osl.iu.edu wrote:
>
> > Author: miked
> > Date: 2012-03-02 10:27:34 EST (Fri, 02 Mar 2012)
> > Ne
0 PM, Jeff Squyres 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, wrote:
>
> > Author: miked (Mike Dubman)
> > Date: 2012-08
e. No type good.
>
> On Aug 4, 2012, at 11:56 AM, "Mike Dubman" wrote:
>
>Hi,
>
> We are switching from datastore (feature we added a couple of
> years ago) to MongoDB NoSQL DB to keep mtt results.
>
> We are adding some "regression" capability ba
there is a die"" in the MongoDB.connect :(
On Mon, Jan 14, 2013 at 4:47 PM, Jeff Squyres (jsquyres) wrote:
> That's weird. Why would an "eval" fix this situation?
>
>
> On Jan 14, 2013, at 8:15 AM, svn-commit-mai...@open-mpi.org wrote:
>
> > Autho
"sh"
from shebang. Somehow and sometimes it can become zombie.
exec =< -Original Message-
> From: Jeff Squyres (jsquyres) [mailto:jsquy...@cisco.com
]
> Sent: Sunday, February 24, 2013 13:10
> To:
> Cc: Mike Dubman
> Subject: fix zombie commit
>
On Mon, Feb 25, 2013 at 6:24 PM, Jeff Squyres (jsquyres) wrote:
> >Looking at the code, you're checking for zombie status before MTT kills
> the proc. Am I reading that right?
>
I don`t think the order matters, if process is not Zombie yet and about to
be killed by MTT later - it is a good flow.
/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:
> Hello,
>
> As on many systems init scripts and the handling of services is based on
> pid files I
ut.
>
>
> On Apr 5, 2014, at 7:27 PM, 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/changeset/1637
> >
> > Log:
> > silence print
>
useful when something goes wrong.
>
> I run Cisco's automated MTT with only --verbose.
>
>
>
> On Apr 7, 2014, at 6:35 PM, Mike Dubman wrote:
>
> > ohh.. it is just flooding the log with same data for every test launch.
> >
> > maybe we should have verbo
we have problems only when adding new code and need to debug it.
will revert back you change.
On Tue, Apr 8, 2014 at 1:58 AM, Jeff Squyres (jsquyres)
wrote:
> On Apr 7, 2014, at 6:39 PM, Mike Dubman wrote:
>
> > somehow we run it with both, --verbose not enough to understand the
&
this commit does more harm then good.
we experience following:
- some child processes still running after timeout and mtt killed the job.
before this commit - it worked fine.
please revert and test more.
On Sat, Jun 21, 2014 at 3:30 PM, MPI Team wrote:
> The branch, master has been updated
>
as to what is happening?
>
> The prior code was killing child processes before mpirun itself, for
> example, which has led MTT to erroneously report that mpirun died right at
> the end of the timeout without being killed. This has been ongoing for
> many months, at a minimum.
>
(jsquyres) wrote:
> On Jun 23, 2014, at 7:47 AM, Mike Dubman wrote:
>
> > after patch, it killed child processes but kept mpirun ... itself.
>
> What does that mean -- are you saying that mpirun is still running? Was
> mpirun sent a signal at all? What kind of message
btw, i think now, when parent process is killed before child, OS makes
child as "" which stick around for good.
On Mon, Jun 23, 2014 at 4:11 PM, Mike Dubman
wrote:
> it seems that mpirun got no signal (no evidence in the log). mtt was
> spinning and mpirun was a only process
> Do you run with --verbose output? MTT should output messages like "***
> Killing mpirun with SIGTERM", and the like. Do you see timeout messages at
> all? I.e., is MTT not entering the timeout code at all?
>
> ...etc.
>
>
>
> On Jun 23, 2014, at 12:16 PM, Da
62 matches
Mail list logo
