I installed mpi4py 1.3 from the tarball download at code.google. The
compiler was gcc 4.6.2, and openmpi version is 1.4.4. Following the
example, I ran runtests.py using -np 5, and I got an error. Looking
through it, the error come from this test
What is odd about this is that it seems only to appear when using five
processors. I've run it using -np 2 3 4 6 7 8. It consistently
succeeds with all other numbers of processors but 5.
I'm at a bit of a loss to see why 5 processors is special, though I
found someone else posted in Sep with a similar problem, but I didn't
see any conclusion/solution posted. There was a suggestion to use the
SVN version, but I'm only finding a mercurial version on code.google.
On Sun, May 20, 2012 at 4:42 PM, Bennet <justben...@gmail.com> wrote:
> I installed mpi4py 1.3 from the tarball download at code.google. The
> compiler was gcc 4.6.2, and openmpi version is 1.4.4. Following the
> example, I ran runtests.py using -np 5, and I got an error. Looking
> through it, the error come from this test
> What is odd about this is that it seems only to appear when using five
> processors. I've run it using -np 2 3 4 6 7 8. It consistently
> succeeds with all other numbers of processors but 5.
> I'm at a bit of a loss to see why 5 processors is special, though I
> found someone else posted in Sep with a similar problem, but I didn't
> see any conclusion/solution posted. There was a suggestion to use the
> SVN version, but I'm only finding a mercurial version on code.google.
> Suggestions, anyone?
> Thanks, -- bennet
> --
> You received this message because you are subscribed to the Google Groups
> "mpi4py" group.
> To post to this group, send email to mpi4py@googlegroups.com.
> To unsubscribe from this group, send email to
> mpi4py+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mpi4py?hl=en.
> I installed mpi4py 1.3 from the tarball download at code.google. The
> compiler was gcc 4.6.2, and openmpi version is 1.4.4. Following the
> example, I ran runtests.py using -np 5, and I got an error. Looking
> through it, the error come from this test
> What is odd about this is that it seems only to appear when using five
> processors. I've run it using -np 2 3 4 6 7 8. It consistently
> succeeds with all other numbers of processors but 5.
> I'm at a bit of a loss to see why 5 processors is special, though I
> found someone else posted in Sep with a similar problem, but I didn't
> see any conclusion/solution posted. There was a suggestion to use the
> SVN version, but I'm only finding a mercurial version on code.google.
> Start with the development version (the mercurial repository), and see if
> the problem is reproducible there.
> A
> On Sun, May 20, 2012 at 4:42 PM, Bennet <justben...@gmail.com> wrote:
> > I installed mpi4py 1.3 from the tarball download at code.google. The
> > compiler was gcc 4.6.2, and openmpi version is 1.4.4. Following the
> > example, I ran runtests.py using -np 5, and I got an error. Looking
> > through it, the error come from this test
> > What is odd about this is that it seems only to appear when using five
> > processors. I've run it using -np 2 3 4 6 7 8. It consistently
> > succeeds with all other numbers of processors but 5.
> > I'm at a bit of a loss to see why 5 processors is special, though I
> > found someone else posted in Sep with a similar problem, but I didn't
> > see any conclusion/solution posted. There was a suggestion to use the
> > SVN version, but I'm only finding a mercurial version on code.google.
> > Suggestions, anyone?
> > Thanks, -- bennet
> > --
> > You received this message because you are subscribed to the Google Groups
> > "mpi4py" group.
> > To post to this group, send email to mpi4py@googlegroups.com.
> > To unsubscribe from this group, send email to
> > mpi4py+unsubscribe@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/mpi4py?hl=en.
Since I also have access to an RH 6 machine, I decided to try
installing there. I built using the RH included python, 2.6.6, using
gcc 4.7.0 and openmpi-1.6.0. I get some additional messages about
infiniband that didn't show up on RH 5. Here's the output to
Lisandro's suggested command line (I only have openmpi, not mpich to
use):
> That is with the version built from the mercurial repository. Again, -
> np 4 runs fine, as does -np 12.
> -- bennet
> On May 20, 10:29 am, Aron Ahmadia <a...@ahmadia.net> wrote:
> > Start with the development version (the mercurial repository), and see if
> > the problem is reproducible there.
> > A
> > On Sun, May 20, 2012 at 4:42 PM, Bennet <justben...@gmail.com> wrote:
> > > I installed mpi4py 1.3 from the tarball download at code.google. The
> > > compiler was gcc 4.6.2, and openmpi version is 1.4.4. Following the
> > > example, I ran runtests.py using -np 5, and I got an error. Looking
> > > through it, the error come from this test
> > > What is odd about this is that it seems only to appear when using five
> > > processors. I've run it using -np 2 3 4 6 7 8. It consistently
> > > succeeds with all other numbers of processors but 5.
> > > I'm at a bit of a loss to see why 5 processors is special, though I
> > > found someone else posted in Sep with a similar problem, but I didn't
> > > see any conclusion/solution posted. There was a suggestion to use the
> > > SVN version, but I'm only finding a mercurial version on code.google.
> > > Suggestions, anyone?
> > > Thanks, -- bennet
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "mpi4py" group.
> > > To post to this group, send email to mpi4py@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > mpi4py+unsubscribe@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/mpi4py?hl=en.
On Sun, May 20, 2012 at 8:48 PM, Bennet <justben...@gmail.com> wrote:
> Since I also have access to an RH 6 machine, I decided to try
> installing there. I built using the RH included python, 2.6.6, using
> gcc 4.7.0 and openmpi-1.6.0. I get some additional messages about
> infiniband that didn't show up on RH 5. Here's the output to
> Lisandro's suggested command line (I only have openmpi, not mpich to
> use):
> > That is with the version built from the mercurial repository. Again, -
> > np 4 runs fine, as does -np 12.
> > -- bennet
> > On May 20, 10:29 am, Aron Ahmadia <a...@ahmadia.net> wrote:
> > > Start with the development version (the mercurial repository), and see
> if
> > > the problem is reproducible there.
> > > A
> > > On Sun, May 20, 2012 at 4:42 PM, Bennet <justben...@gmail.com> wrote:
> > > > I installed mpi4py 1.3 from the tarball download at code.google. The
> > > > compiler was gcc 4.6.2, and openmpi version is 1.4.4. Following the
> > > > example, I ran runtests.py using -np 5, and I got an error. Looking
> > > > through it, the error come from this test
> > > > What is odd about this is that it seems only to appear when using
> five
> > > > processors. I've run it using -np 2 3 4 6 7 8. It consistently
> > > > succeeds with all other numbers of processors but 5.
> > > > I'm at a bit of a loss to see why 5 processors is special, though I
> > > > found someone else posted in Sep with a similar problem, but I didn't
> > > > see any conclusion/solution posted. There was a suggestion to use
> the
> > > > SVN version, but I'm only finding a mercurial version on code.google.
> > > > Suggestions, anyone?
> > > > Thanks, -- bennet
> > > > --
> > > > You received this message because you are subscribed to the Google
> Groups
> > > > "mpi4py" group.
> > > > To post to this group, send email to mpi4py@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > mpi4py+unsubscribe@googlegroups.com.
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/mpi4py?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "mpi4py" group.
> To post to this group, send email to mpi4py@googlegroups.com.
> To unsubscribe from this group, send email to
> mpi4py+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mpi4py?hl=en.
Do you have access to an openmpi version that you can or cannot replicate it with...?
I'd be curious to know if you can replicate with openmpi. If not, then I might try to install mpich2 and see if I can not replicate it here. If I can do that, perhaps it would be worth pursing in the context of openmpi...?
On 20 May 2012 14:56, <justben...@gmail.com> wrote:
> Do you have access to an openmpi version that you can or cannot replicate it
> with...?
I can replicate with OpenMPI 1.5.4 from the Fedora 16 package. This is
not the first time I got issues with OpenMPI that did not appear with
MPICH2, so I'm inclined to say that this issues is in OpenMPI side and
not mpi4py's fault.
Figuring out what's going on will require to write some self-contained
C example, cross fingers to reproduce the issue, then bug Open MPI
folks about it, and so on...
On Sun, May 20, 2012 at 7:51 PM, Aron Ahmadia <a...@ahmadia.net> wrote:
> I'm not sure this is worth tracing down, I can't reproduce it on mpich2
> either.
It also happens with the current hg version of mpi4py and
$ rpm -qa openmpi gcc python
python-2.7.3-6.fc17.x86_64
gcc-4.7.0-5.fc17.x86_64
openmpi-1.5.4-5.fc17.1.x86_64
