[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2009-02-23 Thread Olaf Lenz
So finally it looks as though the bug is neither OpenMPI nor numpy-related, but a problem of pyMPI. As there is no pyMPI package for ubuntu, I mark the bug as invalid. I think you should contact the pyMPI development team if you need to get the bug fixed. If that doesn't help, you could probably

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2009-02-21 Thread gpk
As of yesterday, when I was re-compiling stuff, I have a * 64-bit machine with 64-bit Ubuntu 8.10: works fine. I compile openmpi-1.3.?.(I'm running stuff, and not in a position right now to try the Ubuntu package.) * 64-but machines with 32-bit Ubuntu 8.04: No good, even if I recompile ope

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2009-02-21 Thread Olaf Lenz
In the original bug report you stated, that the bug ocurs on 64bit as well as on 32bit. Does this mean that you were talking about 32bit and 64bit Ubuntu, but always on a 64bit machine? Also, is it connected to pyMPI, or is pure python enough? And have you already checked whether there are any bu

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2009-02-21 Thread Olaf Lenz
Ok, this does make some sort of sense. I would suggest to move the bug to numpy for now. The error message of above seems to show that the error occurs when you use pyMPI. Could you please also test whether the problem occurs also when you use pure python instead of pyMPI? ** Changed in: python

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2009-02-20 Thread gpk
It might be something in the system config, but it's not obvious. The trouble is, aside from pyMPI, it's a professionally maintained Ubuntu system, with no customization other than package selection. It's a 64-bit machine with a 32-bit Ubuntu installation. This seems to be related, perhaps, to

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2008-12-16 Thread Olaf Lenz
Ok, apparently I hadn't read the report carefully enough. Still, everything works fine here: > sudo apt-cache policy python-numpy python-numpy: Installed: 1:1.1.1-1 Candidate: 1:1.1.1-1 Version table: *** 1:1.1.1-1 0 500 http://de.archive.ubuntu.com intrepid/main Packages 10

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2008-12-15 Thread gpk
I suppose this could be a numpy problem, instead of an openMPI problem.It's not an obvious problem because running python -c 'import numpy; numpy.test()' gives no errors. -- Crash with pyMPI that doesn't happen with latest upstream https://bugs.launchpad.net/bugs/307901 You received this bug

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2008-12-15 Thread gpk
You can't reproduce it because the problem doesn't show up in "make check". The problem happens when you import numpy from within pyMPI: mace:~$ pyMPI # THIS STUFF HERE SEEMS TO BE WARNING MESSAGES -- ANNOYING, # BUT NOT THE REAL PROBLEM: libibverbs: Fatal: couldn't read uverbs ABI version.

[Bug 307901] Re: Crash with pyMPI that doesn't happen with latest upstream

2008-12-15 Thread Olaf Lenz
I can't reproduce you problem with Intrepid on 64bit with openmpi and the current pyMPI (2.5b0). I compiled pyMPI via configure and make, and also ran make check (1 of 89 tests fails). > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 8.10 Release: