Re: [OMPI devel] ompi-tests SVN repo has been moved to Github

Two things: 1. Ensure to "git pull --rebase" on your MTT to get the latest updates to MTT. 2. Update your INI files something like this (subset of a patch): [Test get: ibm] module = SCM -scm_module = SVN -scm_url = svn://savbu-usnic.cisco.com/ompi-tests/trunk/ibm +scm_module = Git +scm_url =

Re: [OMPI devel] PSM MTl work with srun launch?

Odd - it used to do the right thing. Looking at the code, it certainly looks like it is doing the right thing. It's using the PMI id as for the first part of the key, and the stepid as the second part. One possibility we've seen with Slurm is that PMI_Init can return true, but actually fail.

[OMPI devel] PSM MTl work with srun launch?

Hi Folks, I'm getting questions about the 1.8.2 and mtl psm and slurm-direct (srun) launch. User is hitting the problem that the global id is not being set. I've suggested for now that the user just set the OMPI_MCA_orte_precondition_transports environment variable for now to something like

Re: [OMPI devel] ompi-tests SVN repo has been moved to Github

Good question. Info coming shortly (i.e., I'm updating mine right now; will share the results). On Sep 16, 2014, at 3:28 PM, Ralph Castain wrote: > And we need to modify our .ini scriptshow? > > On Sep 16, 2014, at 12:22 PM, Jeff Squyres (jsquyres)

[OMPI devel] Git: open-mpi/ompi-tests branch master updated. c2134f3ed25d0b327f631365b6f5f60f4ef7140d

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 project "open-mpi/ompi-tests". The branch, master has been updated via c2134f3ed25d0b327f631365b6f5f60f4ef7140d (commit) from

Re: [OMPI devel] ompi-tests SVN repo has been moved to Github

And we need to modify our .ini scriptshow? On Sep 16, 2014, at 12:22 PM, Jeff Squyres (jsquyres) wrote: > The ompi-tests SVN repo has been moved to Github. The SVN repo is now in > read-only mode. > > Just like the SVN ompi-tests repo, the Github ompi-tests repo is

[OMPI devel] ompi-tests SVN repo has been moved to Github

The ompi-tests SVN repo has been moved to Github. The SVN repo is now in read-only mode. Just like the SVN ompi-tests repo, the Github ompi-tests repo is private. You need to be an active organization in Open MPI to be able to access it. You can use your developer Github ID or you can

Re: [OMPI devel] oshmem-openmpi-1.8.2 causes compile error with -i8(64bit fortarn integer) configuration

I took care of it - thanks! On Sep 16, 2014, at 7:36 AM, tmish...@jcity.maeda.co.jp wrote: > Gilles, > > Your patch looks good to me and I think this issue should be fixed > in the upcoming openmpi-1.8.3. Could you commit it to the trunk and > create a CMR for it? > > Tetsuya > >>

Re: [OMPI devel] 1.8.3rc1 - start your engines

Thanks! On Sep 16, 2014, at 11:40 AM, Paul Hargrove wrote: > The ARM results finished a couple days back and the MIPS results (3 ABIs to > test) finally completed over night. > In the meantime I was able to schedule tests of most of my menagerie of > Intel, PGI, Sun,

Re: [OMPI devel] CONVERSION TO GITHUB

Jeff, So the instructions from your reply is "create a github account if you wish to continue filing tickets". But don't you want/need the trac->github account mapping now to convert existing tickets? For instance, I am "phargrov" in your Trac, but "PHHargrove" at github. And by the way, on

Re: [OMPI devel] CONVERSION TO GITHUB

Not really. One minor point: you'll need a Github account to file Github issues (i.e., what's replacing Trac tickets) and/or use the code commenting tools. On Sep 16, 2014, at 2:33 PM, Paul Hargrove wrote: > Jeff, > > Any instructions for those who have never had

Re: [OMPI devel] 1.8.3rc1 - start your engines

The ARM results finished a couple days back and the MIPS results (3 ABIs to test) finally completed over night. In the meantime I was able to schedule tests of most of my menagerie of Intel, PGI, Sun, Pathscale, and Open64 compilers on x86-64, and some IBM compiler tests on PPC64 (but *NOT* yet

Re: [OMPI devel] CONVERSION TO GITHUB

Jeff, Any instructions for those who have never had Subversion accounts, but do have Trac accounts? You know... the people like me who primarily just make work for others :-) -Paul On Tue, Sep 16, 2014 at 10:34 AM, Jeff Squyres (jsquyres) < jsquy...@cisco.com> wrote: > Short version >

[OMPI devel] CONVERSION TO GITHUB

Short version = - I have added / invited all users to the "ompi" Github repo. *** You need to join and then "unwatch" the "ompi" repo on Github ASAP *** - The github migration is planned for *next* Wednesday: 24 Sep, 2014 ALL OMPI ACTIVITY MUST STOP THAT DAY: commits, tickets,

Re: [OMPI devel] oshmem-openmpi-1.8.2 causes compile error with -i8(64bit fortarn integer) configuration

Gilles, Your patch looks good to me and I think this issue should be fixed in the upcoming openmpi-1.8.3. Could you commit it to the trunk and create a CMR for it? Tetsuya > Mishima-san, > > the root cause is macro expansion does not always occur as one would > have expected ... > > could you

[OMPI devel] OPAL timing framework

Hello, I would like to introduce OMPI timing framework that was included into the trunk yesterday (r32738). The code is new so if you'll hit some bugs - just let me know. The framework consists of the set of macro's and routines for internal OMPI usage + standalone tool mpisync and few

[OMPI devel] race condition in oob/tcp

Ralph, here is the full description of a race condition in oob/tcp i very briefly mentionned in a previous post : the race condition can occur when two not connected orted try to send a message to each other for the first time and at the same time. that can occur when running mpi helloworld on