Re: [MTT devel] mtt/server/gds

PM To: Development list for the MPI Testing Tool mailto:mtt-devel@lists.open-mpi.org> > Subject: Re: [MTT devel] mtt/server/gds   What "gds" directory are you talking about? Can you provide the full path to it? On Jul 25, 2019, at 11:04 AM, Rezanka, Deb via mtt-devel mailto:mtt-devel@list

Re: [MTT devel] mtt/server/gds

Testing Tool mailto:mtt-devel@lists.open-mpi.org> > Subject: Re: [MTT devel] mtt/server/gds  What "gds" directory are you talking about? Can you provide the full path to it? On Jul 25, 2019, at 11:04 AM, Rezanka, Deb via mtt-devel mailto:mtt-devel@lists.open-mpi.org> > wro

Re: [MTT devel] mtt/server/gds

, 2019 at 12:13 PM To: Development list for the MPI Testing Tool Subject: Re: [MTT devel] mtt/server/gds What "gds" directory are you talking about? Can you provide the full path to it? On Jul 25, 2019, at 11:04 AM, Rezanka, Deb via mtt-devel mailto:mtt-devel@lists.open-mpi.org>> wro

Re: [MTT devel] mtt/server/gds

i.org/mailman/listinfo/mtt-devel _______ mtt-devel mailing list mtt-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/mtt-devel

[MTT devel] mtt/server/gds

Does anyone know if the gds directory is being used at all? If not, could we get rid of it. -- Deb Rezanka B Schedule HPC-ENV Office 9, 2nd floor Research Park TA-03, Building 4200, Room 203 Los Alamos National Laboratory ___ mtt-devel mailing list mtt

Re: [MTT devel] MTT Skype Meeting

Try again From: mtt-devel [mailto:mtt-devel-boun...@lists.open-mpi.org] On Behalf Of Rezanka, Deb via mtt-devel Sent: Tuesday, November 6, 2018 11:27 AM To: Van Dresser, Daniel N Cc: Rezanka, Deb ; mtt-devel@lists.open-mpi.org Subject: [MTT devel] MTT Skype Meeting Hi, I have been trying to

[MTT devel] MTT Skype Meeting

Hi, I have been trying to join the meeting today but could not seem to connect either through skype on the computer or over the phone. I had some questions about the TestRun allocate_cmd, deallocate_cmd. Using command = mpirun in [LauncherDefaults] does not do the test runs in the slurm alloc

Re: [MTT devel] MTT docs now online

.org>> > Date: Thursday, July 12, 2018 at 9:04 AM > To: Development list for the MPI Testing Tool <mailto:mtt-devel@lists.open-mpi.org>>, MTT Users > mailto:mtt-us...@lists.open-mpi.org>> > Subject: [MTT devel] MTT docs now online > > We finall

Re: [MTT devel] MTT docs now online

sting Tool , MTT Users Subject: [MTT devel] MTT docs now online We finally got the bugs out and the documentation for Python MTT implementation is now online at https://open-mpi.github.io/mtt. It also picked up the Perl stuff, but we’ll just ignore that little detail :-) Thanks to Akshaya Jag

[MTT devel] MTT docs now online

We finally got the bugs out and the documentation for Python MTT implementation is now online at https://open-mpi.github.io/mtt . It also picked up the Perl stuff, but we’ll just ignore that little detail :-) Thanks to Akshaya Jagannadharao for all the hard work t

Re: [MTT devel] MTT / Open MPI Visibility of New Failures

We are putting a pin in this for now. Amazon had an idea they wanted to run with and report back. Once they have more info then we'll try to setup another meeting. On Tue, Jul 11, 2017 at 3:20 PM, Josh Hursey wrote: > In the Open MPI face-to-face meeting we had a long discussion about how to > b

[MTT devel] MTT / Open MPI Visibility of New Failures

In the Open MPI face-to-face meeting we had a long discussion about how to better harness MTT such that new failures are identified and the community alerted to their existence. The current manual way is not working. Our ultimate goal here is to know if we are making forward progress, and if someth

[MTT devel] MTT Spreadsheet / Python client

Hello, This email only affects people working on the python client. I have attached the spreadsheet we spoke about this morning. Any input will be helpful but there are a few specific questions. On the .INI sections page of the spreadsheet column F, status. Could you check the items in red (an

[MTT devel] MTT ompi-tests password

Folks -- In helping someone get up to speed with MTT yesterday, I updated an MTT sample .ini file and accidentally committed the ompiteam-mtt Github password to the public repository. :-( I have therefore just changed the password for the ompiteam-mtt account. Please contact me off-list for

[MTT devel] MTT DB Archive 2011-2013

(Noting this here for the mailing list archives) To free up some space on the MTT Server I archived the 2011-2013 tables (adding to the archive from 2006-2010). The archived tables are located at the /nfs/data/jjhursey/mtt-archive mount on the MTT server. I like keeping the old tables around in ca

Re: [MTT devel] [MTT commits] Git: open-mpi/mtt branch master updated. f846c3c2bb57155c2123f8ea4fc6b608a2c37655

Mike -- If you're going to change the behavior, please also change the comment. > On Feb 8, 2015, at 10:11 AM, git...@crest.iu.edu wrote: > > This is an automated email from the git hooks/post-receive script. It was > generated because a ref change was pushed to the repository containing > the

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 313f269f46faa4e797ef48791baac659f5cc93ea

Good catch; thanks. On Jul 13, 2014, at 7:35 AM, MPI Team wrote: > The branch, master has been updated > via 313f269f46faa4e797ef48791baac659f5cc93ea (commit) > from ec7436085d39893e9e87369801b8db44c2e57d14 (commit) > > Those revisions listed above that are new to this repository h

Re: [MTT devel] MTT: let's use git tags

; > To: "Development list for the MPI Testing Tool" > Sent: Thursday, June 26, 2014 2:47:35 PM > Subject: Re: [MTT devel] MTT: let's use git tags > > Published Git tags are *not* movable (by design). You're better off making it > a branch that you treat li

Re: [MTT devel] MTT: let's use git tags

[1] http://ariya.ofilabs.com/2013/09/fast-forward-git-merge.html - Original Message - From: "Gilles Gouaillardet" To: "Development list for the MPI Testing Tool" Sent: Monday, June 30, 2014 4:06:34 AM Subject: Re: [MTT devel] MTT: let's use git tags Jeff, Wh

Re: [MTT devel] MTT: let's use git tags

--- Original Message - > From: "Dave Goodell (dgoodell)" > To: "Development list for the MPI Testing Tool" > Sent: Thursday, June 26, 2014 2:47:35 PM > Subject: Re: [MTT devel] MTT: let's use git tags > > Published Git tags are *not* movable (by de

Re: [MTT devel] MTT: let's use git tags

odell (dgoodell)" To: "Development list for the MPI Testing Tool" Sent: Thursday, June 26, 2014 2:47:35 PM Subject: Re: [MTT devel] MTT: let's use git tags Published Git tags are *not* movable (by design). You're better off making it a branch that you treat like a tag, if that

Re: [MTT devel] MTT: let's use git tags

Published Git tags are *not* movable (by design). You're better off making it a branch that you treat like a tag, if that's your desire. Even then, you might confuse someone who is less familiar with Git in some cases if you move that branch around. -Dave > On Jun 26, 2014, at 6:06 AM, "Jeff S

Re: [MTT devel] MTT: let's use git tags

I've thought about this a little, and I'm still inclined to use the simple/lazy method of tags on master. Some random points, in no particular order: 1. master should always be for development, IMHO. If we start using a multi-branch scheme, then the branches should be for releases, etc. 2. MT

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

Ok, thanks. In the meantime, please roll back to the v3.0.0 tag and you should be good. Sorry for the hassle. :-( On Jun 25, 2014, at 12:19 AM, Mike Dubman wrote: > Hi > sorry for incomplete description. will trace problem more closely later next > week and provide. > > M > > > On Mon,

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

Hi sorry for incomplete description. will trace problem more closely later next week and provide. M On Mon, Jun 23, 2014 at 10:13 PM, Jeff Squyres (jsquyres) < jsquy...@cisco.com> wrote: > Ok, just got in to Chicago from my flight and am back online. > > Mike: you are still not providing very m

Re: [MTT devel] MTT: let's use git tags

+1 for using branches : branch usage is less error prone plus git makes branching unexpensive. as far as i am concerned, i'd rather have the default master branch is the for the "stable" version and have one branch called devel (or dev, or whatever) : - git clone => get the stable (aka master) bra

Re: [MTT devel] MTT: let's use git tags

PI Testing Tool" Sent: Tuesday, June 24, 2014 5:49:34 PM Subject: [MTT devel] MTT: let's use git tags The topic came up today that MTT sometimes has bugs, particularly w.r.t. ongoing MTT development. It seems like we should use git tags to let the OMPI/testing community know which tag t

[MTT devel] MTT: let's use git tags

The topic came up today that MTT sometimes has bugs, particularly w.r.t. ongoing MTT development. It seems like we should use git tags to let the OMPI/testing community know which tag they should be using (vs. HEAD). To that end, I have created a "v3.0.0" tag that exists before the controversia

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

Ok, just got in to Chicago from my flight and am back online. Mike: you are still not providing very much information. :-\ Your first mails make it seem like MTT is continuing to run, but leaving "launchers" (assumedly mpirun processes) still running, but they have no children. Which would be

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

On Jun 23, 2014, at 8:48 AM, Mike Dubman wrote: > btw, i think now, when parent process is killed before child, OS makes child > as "" which stick around for good. The grandparent should inherit the child. If the grandparent then does not wait(2) on the child, then the child will remain a zom

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

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 who left on the nod

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

it seems that mpirun got no signal (no evidence in the log). mtt was spinning and mpirun was a only process who left on the node. It was unclear why mtt did not kill mpirun. will try to extract perl stacktrace from mtt on tomorrow`s nightly run. On Mon, Jun 23, 2014 at 2:59 PM, Jeff Squyres (jsqu

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

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 messages are being displayed? ...etc. The commits fix import

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

after patch, it killed child processes but kept mpirun ... itself. before that patch - all processes were killed (and you are right, "mpirun died right at the end of the timeout" was reported) but at least it left the cluster in the clean state w/o leftovers. now many "orphan" launchers are alive

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

There was actually quite a bit of testing before this was committed. This commit resolved a lot of hangs across multiple organizations. Can you be more specific as to what is happening? The prior code was killing child processes before mpirun itself, for example, which has led MTT to erroneous

Re: [MTT devel] [MTT svn] GIT: MTT branch master updated. 016088f2a0831b32ab5fd6f60f4cabe67e92e594

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 >

[MTT devel] MTT moved to final github location

https://github.com/open-mpi/mtt The MTT SVN is now read-only. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

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 > problem and -

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

On Apr 7, 2014, at 6:39 PM, Mike Dubman wrote: > somehow we run it with both, --verbose not enough to understand the problem > and --debug is too much. > > maybe --trace is here to rescue? It won't really solve the problem; it'll just create another level of argument about where a given messa

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

; $str; > > > } > > > > > > _______ > > > mtt-svn mailing list > > > mtt-...@open-mpi.org > > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-svn > > > > > > -- > > Jeff Squyre

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

$str\n"); > > +#Debug("Functions::MPI::OMPI: Returning MCA params $str\n"); > > $str; > > } > > > > ___ > > mtt-svn mailing list > > mtt-...@open-mpi.org > >

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

ohh.. it is just flooding the log with same data for every test launch. maybe we should have verbose level in mtt? On Mon, Apr 7, 2014 at 6:30 PM, Jeff Squyres (jsquyres) wrote: > Mike -- > > Why did you comment these out? By definition, --debug output should be a > LOT of output. > > > On Apr

Re: [MTT devel] [MTT svn] svn:mtt-svn r1637 - trunk/lib/MTT/Values/Functions/MPI

Mike -- Why did you comment these out? By definition, --debug output should be a LOT of output. 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 >

Re: [MTT devel] mtt-relay patch - create pid file when run as daemon

> > Christoph Niethammer > High Performance Computing Center Stuttgart (HLRS) > Nobelstrasse 19 > 70569 Stuttgart > > Tel: ++49(0)711-685-87203 > email: nietham...@hlrs.de > http://www.hlrs.de/people/niethammer > ___ >

Re: [MTT devel] mtt-relay patch - create pid file when run as daemon

/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

[MTT devel] mtt-relay patch - create pid file when run as daemon

Hello, As on many systems init scripts and the handling of services is based on pid files I extended the mtt-relay script as follows: If run with the --daemon option * Create file /var/run/mtt-relay.pid if it does not exist and write the pid of the background process into it. * exit with retur

Re: [MTT devel] MTT feature request

Hi Jeff, Cool, no worries. I just didn't want to forget. Thanks, --tjn _ Thomas Naughton naught...@ornl.gov Research Associate (865) 576-4184 On

Re: [MTT devel] MTT feature request

Finally done -- sorry for the delay! On Apr 10, 2013, at 11:18 AM, Thomas Naughton wrote: > Hi Jeff, > > Do you know if the 'email_detailed_report_onfail' request for MTT ever got > a green light? I just checked and didn't see it in trunk. > > Quick refresher summary: > + Adds new 'email_deta

Re: [MTT devel] MTT feature request

Hi Jeff, Do you know if the 'email_detailed_report_onfail' request for MTT ever got a green light? I just checked and didn't see it in trunk. Quick refresher summary: + Adds new 'email_detailed_report_onfail' flag to TextReporter that only sends detailed report if the test was not "success"

Re: [MTT devel] MTT feature request

Hi Jeff, Sorry for the delay in replying to this; somehow this mail slipped by me. No problem-o. :-) Yes, I just updated local checkout and appears to be just fine with latest trunk. Thanks, --tjn _ Thomas Naught

Re: [MTT devel] MTT feature request

Sorry for the delay in replying to this; somehow this mail slipped by me. I'm all for what you described. Does your patch still apply to the current trunk? (Texteeporter was just recently split up a bit) Sent from my phone. No type good. On Feb 28, 2013, at 10:07 PM, "Thomas Naughton" wrote

Re: [MTT devel] [MTT svn] svn:mtt-svn r1607 - in trunk/lib/MTT: Reporter Values/Functions

This is a bad commit: Global symbol "$url" requires explicit package name at /opt/local/lib/perl5/site_perl/5.12.4/MTT/Values/Functions/Icc_codecov.pm line 107. Please fix. On Mar 25, 2013, at 12:07 PM, svn-commit-mai...@open-mpi.org wrote: > Author: miked (Mike Dubman) > Date: 2013-03-25 12

Re: [MTT devel] [MTT svn] svn:mtt-svn r1602 - in trunk/lib/MTT: . Reporter

Awesome. +1! On Mar 18, 2013, at 11:27 PM, wrote: > Author: miked (Mike Dubman) > Date: 2013-03-19 02:27:03 EDT (Tue, 19 Mar 2013) > New Revision: 1602 > URL: https://svn.open-mpi.org/trac/mtt/changeset/1602 > > Log: > fixes #1971 > Add new reporter HTMLReport.pm; > Took TextReporter.pm and de

Re: [MTT devel] [MTT svn] svn:mtt-svn r1575 - trunk/lib/MTT/Reporter

Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.o

Re: [MTT devel] [MTT svn] svn:mtt-svn r1575 - trunk/lib/MTT/Reporter

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: > > > Author: miked (Mike Dubman) > > Date: 2013-01-14 08:1

Re: [MTT devel] [MTT svn] svn:mtt-svn r1575 - trunk/lib/MTT/Reporter

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: > Author: miked (Mike Dubman) > Date: 2013-01-14 08:15:54 EST (Mon, 14 Jan 2013) > New Revision: 1575 > URL: https://svn.open-mpi.org/trac/mtt/changeset/1575 > > Log: > fixe

Re: [MTT devel] [MTT svn] svn:mtt-svn r1535 - trunk/lib/MTT

What was wrong with @param@ processing? Please, please, please provide more detail in your commit messages. :-( On Oct 2, 2012, at 8:35 AM, wrote: > Author: miked (Mike Dubman) > Date: 2012-10-02 08:35:58 EDT (Tue, 02 Oct 2012) > New Revision: 1535 > URL: https://svn.open-mpi.org/trac/mtt/cha

Re: [MTT devel] [MTT svn] svn:mtt-svn r1481 - in trunk: client lib/MTT/Reporter

Sweet. On Aug 6, 2012, at 2:42 AM, Mike Dubman wrote: > sure, it is already in the trunk - we are polishing the whole use-case and > once working fine - will add some docs. > > On Sat, Aug 4, 2012 at 7:40 PM, Jeff Squyres (jsquyres) > wrote: > Sounds sweet! > > Will you guys be contributing

Re: [MTT devel] [MTT svn] svn:mtt-svn r1481 - in trunk: client lib/MTT/Reporter

sure, it is already in the trunk - we are polishing the whole use-case and once working fine - will add some docs. On Sat, Aug 4, 2012 at 7:40 PM, Jeff Squyres (jsquyres) wrote: > Sounds sweet! > > Will you guys be contributing This stuff, perchance? > > Sent from my phone. No type good. > > On

Re: [MTT devel] [MTT svn] svn:mtt-svn r1481 - in trunk: client lib/MTT/Reporter

Sounds sweet! Will you guys be contributing This stuff, perchance? Sent from my phone. No type good. On Aug 4, 2012, at 11:56 AM, "Mike Dubman" mailto:mike.o...@gmail.com>> wrote: Hi, We are switching from datastore (feature we added a couple of years ago) to MongoDB NoSQL DB to keep mtt res

Re: [MTT devel] [MTT svn] svn:mtt-svn r1481 - in trunk: client lib/MTT/Reporter

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 based on MTT and MongoDB reporter: - run mtt - when mtt finishes, extract results for previous runs of the same test with same paramet

Re: [MTT devel] [MTT svn] svn:mtt-svn r1481 - in trunk: client lib/MTT/Reporter

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-01 05:46:03 EDT (Wed, 01 Aug 2012) > New Revision: 1481 > URL: https://svn.open-

Re: [MTT devel] MTT queries... problems

Weird. I was able to reproduce. I suspect that there is probably a bug somewhere in the uglier magic in the reporter. It is tricky the way the reporter handles multiple pages of results. Unfortunately, I don't think anyone understands that code any more (it -really- needs to be reworked). I'm not

[MTT devel] MTT queries... problems

I seem to get unreliable results from MTT queries. To reproduce: - go to http://www.open-mpi.org/mtt - click on "Test run" - for "Date range:" enter "2012-03-23 00:30:00 - 2012-03-23 23:55:00" - for "Org:" enter "oracle" - for "Platform name:" enter "t2k-0" - for "Suite:" enter "ibm-32" - click o

Re: [MTT devel] [MTT svn] svn:mtt-svn r1440

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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1440

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) > New Revision: 1440 > URL: https://svn.open-mpi.org/trac/mtt/changeset/1440 > > Log: > Now it

Re: [MTT devel] [MTT svn] svn:mtt-svn r1433

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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1433

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* documentation; it's important to keep it up to date. Thanks! On Jan 25, 2012, at 6:02 AM, mi...@osl.iu.edu wrote: > Author:

Re: [MTT devel] [MTT svn] svn:mtt-svn r1400

Good database side stuff coming soon. Stay tuned :) On Thu, Aug 18, 2011 at 1:21 PM, Jeff Squyres wrote: > Awesome.  :-) > > On Aug 18, 2011, at 1:20 PM, jjhur...@osl.iu.edu wrote: > >> Author: jjhursey >> Date: 2011-08-18 13:20:35 EDT (Thu, 18 Aug 2011) >> New Revision: 1400 >> URL: https://svn.

Re: [MTT devel] [MTT svn] svn:mtt-svn r1400

Awesome. :-) On Aug 18, 2011, at 1:20 PM, jjhur...@osl.iu.edu wrote: > Author: jjhursey > Date: 2011-08-18 13:20:35 EDT (Thu, 18 Aug 2011) > New Revision: 1400 > URL: https://svn.open-mpi.org/trac/mtt/changeset/1400 > > Log: > Add support for Summary tables. > > * Improve the reporting of exec

Re: [MTT devel] [MTT svn] svn:mtt-svn r1385

Rainer -- This is not enough; you also need to close stdin, stdout, and stderr. I also don't think we want to print something to stdout from the child -- it's a race condition. On Feb 23, 2011, at 9:17 AM, rusra...@osl.iu.edu wrote: > Author: rusraink > Date: 2011-02-23 09:17:50 EST (Wed, 2

Re: [MTT devel] mtt eval problem on new perl

l version and the > exact error message? > > Thanks, > Ethan > > > > > >10x > >M > > > ___________ > > mtt-devel mailing list > > mtt-de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo

Re: [MTT devel] mtt eval problem on new perl

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 with >RHEL6, SLES11. > >The simple reproduce is: > >np=&step() > >It seems new perl does not like eval way used in mtt. > >any thoughts?

[MTT devel] mtt eval problem on new perl

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

Re: [MTT devel] mtt questions

me reason that does not work, let us know since it is something > that needs to be fixed since the MTT client should be flexible enough to > support a wide manner of middleware. > > > > -- Josh > > > > > > > > -- > > > Jeff Squyres > > > jsquy...@cisco.com > > > For corpora

Re: [MTT devel] mtt questions

On Jan 5, 2011, at 7:35 AM, Mike Dubman wrote: > Also, found following inside RunEngine.pm code: > > # Set some thresholds for an early exit > my $break_threshold; > $break_threshold->{MTT::Values::PASS} = Value($ini, $section, > "break_threshold_pass"); > $break_threshold->{MTT::Values::FA

Re: [MTT devel] mtt questions

___ > > mtt-devel mailing list > > mtt-de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel > > > > > Joshua Hursey > Postdoctoral Research Associate > Oak Ridge National Laborator

Re: [MTT devel] mtt questions

Thanks for info! Josh, can you please send me mtt.ini file you used with C/R tests as a reference for using non-MPI application? Also, found following inside RunEngine.pm code: # Set some thresholds for an early exit my $break_threshold; $break_threshold->{MTT::Values::PASS} = Value($ini, $s

Re: [MTT devel] mtt questions

On Jan 4, 2011, at 8:04 AM, Jeff Squyres wrote: > On Jan 4, 2011, at 7:06 AM, Mike Dubman wrote: > >> 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% > > I don't recall an opti

Re: [MTT devel] mtt questions

On Jan 4, 2011, at 7:06 AM, Mike Dubman wrote: > 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% I don't recall an option like that, offhand. > Also, are there any ini files example

[MTT devel] mtt questions

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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1377

Ok, that's what I thought, but your comment doesn't seem to match this: # mtt_switch(@np@, 9, "return1", 100, return2", "default", 0); You have an extra "return" in there, and the 5th argument doesn't seem to be quoted properly. On Jan 3, 2011, at 8:21 AM, Mike Dubman wrote: > Hi, > it is c-

Re: [MTT devel] [MTT svn] svn:mtt-svn r1377

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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1377

Mike -- Can you explain this one a little? I don't understand the example you gave in the comment. Also, are you adding all the new funclets to the wiki documentation? On Dec 29, 2010, at 3:52 AM, mi...@osl.iu.edu wrote: > Author: miked > Date: 2010-12-29 03:52:24 EST (Wed, 29 Dec 2010) >

Re: [MTT devel] MTT Database Maintenance: Yearly Reminder

I took care of this for 2011. The database should be all set for the new year. We'll find out next week if there were any issues (keep your fingers crossed). -- Josh On Dec 29, 2010, at 4:00 AM, wrote: > Remember to load the partition tables for 2011! > > -- MTT Development Team > > __

Re: [MTT devel] MTT GDS -- one more...

On Feb 21, 2010, at 5:52 AM, Mike Dubman 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 > > today abo

Re: [MTT devel] MTT GDS -- one more...

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 > >

Re: [MTT devel] MTT GDS -- one more...

On Feb 12, 2010, at 11:35 AM, Andrew Senin wrote: > I worked with Igor on the GDS framework (although Igor knows more tech > details than me). Let me put my two cents to the discussion. Thanks! > > 1. It looks like the main benefits of using the Google App Engine -- > specifically for MTT -- is

Re: [MTT devel] MTT GDS -- one more...

user could (by mistake or on purpose) break links between objects. Regards, Andrew Senin -Original Message- List-Post: mtt-devel@lists.open-mpi.org Date: Thu, 11 Feb 2010 21:43:21 -0500 From: Jeff Squyres Subject: [MTT devel] MTT GDS -- one more... To: Development list for the MPI Testing Too

[MTT devel] MTT GDS -- one more...

Heh... even more questions... (BTW, Ethan and I have asked s many questions that if it helps, I can setup a webex and we can all discuss this in person rather than via 1,000,000 annoying emails from us. :-) Webex can call you; no one will need to pay for an international call) 1. It look

Re: [MTT devel] mtt not working on sles 11up2 perl 5.10.0

Hmm. This is trunk, I assume? If so, Values.pm:107 is: my $ret = _eval_func($func_name, $func_args); # If we got a string back, append the remaining and loop # around looking for more &funclets. --> if (ref($ret) eq "") { - So it's the return of evaluating

[MTT devel] mtt not working on sles 11up2 perl 5.10.0

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

[MTT devel] MTT Database updated for 2010

I just added the 2010 partition tables to the MTT database at IU. So we should be all set for another year of testing. I committed (r1340) a README to the MTT repository with a step-by-step walkthrough of how to add the tables. -- Josh

Re: [MTT devel] [MTT svn] svn:mtt-svn r1320

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

Re: [MTT devel] [MTT svn] svn:mtt-svn r1320

Should &shell() be deprecated? It looks awfully similar to &executable(). -Ethan On Tue, Sep/29/2009 08:34:44AM, mi...@osl.iu.edu wrote: > Author: miked > Date: 2009-09-29 08:34:44 EDT (Tue, 29 Sep 2009) > New Revision: 1320 > URL: https://svn.open-mpi.org/trac/mtt/changeset/1320 > > Log: > appl

Re: [MTT devel] [MTT svn] svn:mtt-svn r1319

On Sep 28, 2009, at 4:20 PM, Ethan Mallove wrote: I was commenting on both r1304 and r1319. These INI params: on_start on_stop are very similar to these INI params: after_each_exec before_any_exec after_all_exec My thought was that it would make sense for them to use a similar nam

Re: [MTT devel] [MTT svn] svn:mtt-svn r1319

>+# EOT >> >+# on_stop=&shell_script("mtt",myscript) >> > +# >> >+# >> >+ >> > +sub shell_script { >> >+ * * * my ($cmd_section, $cmd_param) = @_; >> >

Re: [MTT devel] [MTT svn] svn:mtt-svn r1319

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 might be left over from 1960. :-)

Re: [MTT devel] [MTT svn] svn:mtt-svn r1319

http://www.open-mpi.org/mailman/listinfo.cgi/mtt-svn > > -- > Jeff Squyres > jsquy...@cisco.com > > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/

Re: [MTT devel] [MTT svn] svn:mtt-svn r1319

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 might be left over from 1960. :-) But the nice thing is that you then don't have to identify /bin/

  1   2   3   >