[MTT devel] Fwd: [MTT commits] Git: open-mpi/mtt branch gh-pages updated. a919925665b72524e7c77358c94c1d677900156b

Is there a way, perchance, to not re-generate / re-push the docs if nothing meaningful changes? E.g., this commit is just changing the date, but no other content changed. Begin forwarded message: From: gitdub-nore...@aws.open-mpi.org ('Gitdub ')

[MTT devel] This list is migrating!

Short version = The server for this mailing list will be migrating sometime soon (the exact timing is not fully predictable). Three things you need to know: 1. We'll send a "This list is now closed for migration" last message when the migration starts 2. We'll send a "This list is

[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

Re: [MTT devel] GitHub Issue Cleanup

+1 > On May 13, 2016, at 2:27 PM, Ralph Castain wrote: > > +1 on all these > > Thanks for taking point, Josh! > >> On May 13, 2016, at 11:08 AM, Josh Hursey wrote: >> >> We are seeing more activity with MTT development, and there is a desire to >>

Re: [MTT devel] [OMPI devel] mtt-submit, etc.

I see the issue in the current code: 1. The current code assumes that if you use the MTT database reporter, you can reach the database. One of the first things it does is ping the server to ensure that it's reachable. The rationale is that you don't want MTT to run for a long time and then

[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

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

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?

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

Re: [MTT devel] Converted to git

! On Apr 16, 2014, at 3:40 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > BTW, I used the following SVN<-->email addresses mapping for creating the git > commits. Let me know if you want something different: > > adkulkar = Abhishek Kulkarni <adkul...@cs.india

Re: [MTT devel] Converted to git

Hursey <jjhur...@open-mpi.org> jsquyres = Jeff Squyres <jsquy...@cisco.com> miked = Mike Dubman <mi...@mellanox.com> pasha = Pavel Shamis <sham...@ornl.gov> rusraink = Rainer Keller <rainer.kel...@hft-stuttgart.de> shiqing = Shiqing Fan <f...@hlrs.de> timattox =

[MTT devel] Converted to git

I have done a TRIAL conversion to git and pushed it to a demo repo at github. Please examine it and let me know if you see any problems: https://github.com/jsquyres/mtt-test Note that we converted references to "rXYZ" in log messages -- see

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

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

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) <jsquy...@cisco.com> > wrote: > Mike -- > > Why did you comment these out? By definition, --debug output should be a LOT &g

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:

[MTT devel] Migrating www.open-mpi.org

All -- Our hosting provider will be migrating www.open-mpi.org to a new machine on Wednesday. See message below for details. Begin forwarded message: From: DongInn Kim > Subject: Migrating

Re: [MTT devel] fix zombie commit

On Feb 26, 2013, at 2:11 AM, Mike Dubman <mi...@dev.mellanox.co.il> wrote: > On Mon, Feb 25, 2013 at 6:24 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > >Looking at the code, you're checking for zombie status before MTT kills the > >proc. Am I readi

Re: [MTT devel] fix zombie commit

On Feb 24, 2013, at 6:59 AM, Mike Dubman wrote: > What protection do you mean? Check that /proc/pid/status exists? It is done > in Grep() Ah, excellent -- I hadn't noticed that. > We observe that process which was launched by mtt and hangs (mtt detect > timeout and

[MTT devel] fix zombie commit

Mike -- Please protect this code better; MTT is also run on Solaris and OS X. Also, can you describe more fully the case where zombies are being left behind by MTT? On Feb 24, 2013, at 1:44 AM, wrote: > Author: miked (Mike Dubman) > Date: 2013-02-24 01:44:31

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

Wow! Icky. That should be reported upstream. On Jan 15, 2013, at 1:28 PM, Mike Dubman <mi...@dev.mellanox.co.il> wrote: > there is a die"" in the MongoDB.connect :( > > On Mon, Jan 14, 2013 at 4:47 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> >

[MTT devel] Broken MTT trunk

It looks like some of my recent commits have broken the trunk. I'll be looking at this today. But it might be safest for those running off the trunk to update to a few days ago. Sent from my phone. No type good.

Re: [MTT devel] MTToGDS

m>; Igor Ivanov <igor.iva...@argus-cv.com>; Development list for the MPI Testing Tool <mtt-de...@open-mpi.org>; mtt-devel-boun...@open-mpi.org <mtt-devel-boun...@open-mpi.org>; Mike Dubman <mi...@voltaire.com>; Jeff Squyres (jsquyres) Sent: Thu Mar 04 01:31:16 2010

Re: [MTT devel] MTToGDS

om> Cc: b...@argus-cv.com <b...@argus-cv.com>; Igor Ivanov <igor.iva...@argus-cv.com>; Development list for the MPI Testing Tool <mtt-de...@open-mpi.org>; yift...@voltaire.com <yift...@voltaire.com>; Mike Dubman <mi...@voltaire.com>; Jeff Squyres (jsquyres) Se

Re: [MTT devel] OTF testing tool

That sounds yummy - andreas can you help out with how to invoke the otf tool? -jms Sent from my PDA. No type good. - Original Message - From: mtt-devel-boun...@open-mpi.org To: Development list for the MPI Testing Tool Cc: