capturing in the bug is good enough for me at this point, thanks Jeff
Jeff Squyres wrote:
Ok:
https://svn.open-mpi.org/trac/ompi/ticket/1375
I think any of us could do this -- it's pretty straightforward. No
guarantees on when I can get to it; my 1.3 list is already pretty long...
On Jul 3
Thanks Ralph, this fix does the trick.
Aurelien
Le 3 juil. 08 à 13:53, r...@osl.iu.edu a écrit :
Author: rhc
Date: 2008-07-03 13:53:37 EDT (Thu, 03 Jul 2008)
New Revision: 18804
URL: https://svn.open-mpi.org/trac/ompi/changeset/18804
Log:
Repair the MPI-2 dynamic operations. This includes:
1
Ok:
https://svn.open-mpi.org/trac/ompi/ticket/1375
I think any of us could do this -- it's pretty straightforward. No
guarantees on when I can get to it; my 1.3 list is already pretty long...
No problem. I will take this one.
Pasha.
On Jul 3, 2008, at 6:20 AM, Pavel Shamis (Pasha) wr
The problem has now been fixed.
Please let us know if you run into any further issues with the new
version of trac.
On Jul 3, 2008, at 2:48 PM, Jeff Squyres wrote:
I just did a commit and got the same error. I'll followup with the
IU admins; something probably didn't upgrade properly on
Ok:
https://svn.open-mpi.org/trac/ompi/ticket/1375
I think any of us could do this -- it's pretty straightforward. No
guarantees on when I can get to it; my 1.3 list is already pretty
long...
On Jul 3, 2008, at 6:20 AM, Pavel Shamis (Pasha) wrote:
Jeff Squyres wrote:
Do you need c
I just did a commit and got the same error. I'll followup with the IU
admins; something probably didn't upgrade properly on the SVN side of
the post-commit-hooks or somesuch.
On Jul 3, 2008, at 10:58 AM, Ralph Castain wrote:
Not sure if anyone else is seeing this, but I got a strange error
Not sure if anyone else is seeing this, but I got a strange error output
immediately following my last commit to the trunk:
Warning: 'post-commit' hook failed with error output:
Traceback (most recent call last):
File "/opt/shnadm/rep/ompi/hooks/trac-post-commit-hook", line 200, in ?
CommitH
On Thu, Jul 03, 2008 at 05:56:52AM -0700, Jeff Squyres wrote:
> - I know that leave_pinned is frequently meaningless to real apps
> (although Torsten likes to argue otherwise -- and he's got at least
> some real-world data points that show otherwise :-) ).
I don't want to argue otherwise based
As long as we don't go back to libptmalloc2 linked into libmpi, I don't
have strong objections.
Brian
On Thu, 3 Jul 2008, Jeff Squyres wrote:
WHAT: make mpi_leave_pinned=1 by default when a BTL is used that would
benefit from it (when possible; 0 when not, obviously)
WHY: Several reasons:
Jeff Squyres wrote:
Do you need configury to disable building ibcm / rdmacm support?
The more I think about it, the more I think that these would be good
features to have for v1.3...
I had similar issue recently. It will be nice to have option to
disable/enable *CM via config flags.
On Jul
WHAT: make mpi_leave_pinned=1 by default when a BTL is used that would
benefit from it (when possible; 0 when not, obviously)
WHY: Several reasons:
- we continually get beat up because of "lower performance" on
benchmarks by default (I get beat up, at least ;-) )
- ptmalloc is no longer compi
Do you need configury to disable building ibcm / rdmacm support?
The more I think about it, the more I think that these would be good
features to have for v1.3...
On Jul 3, 2008, at 2:52 AM, Don Kerr wrote:
I did not think it was required but it hung me up when I built ompi
on one system
I did not think it was required but it hung me up when I built ompi on
one system which had the ibcm libraries and then ran on a system without
the ibcm libs. I had another issue on the system without ibcm libs which
prevented my building there but I will go down that path again. Thanks.
Jeff
13 matches
Mail list logo
