For those playing with the current 1.3 branch, just a little "heads
up". There is a missing commit that needs to be moved across from the
trunk that is causing the branch to simply exit after printing a
debug. I am merging the necessary patch across now, but have to
rebuild to verify before
I explained the change in the commit message to r19097, but just in
case you missed it, here is an abridged version:
Per the July technical meeting:
Standardize the handling of the orte launch agent option across PLMs.
This has been a consistent complaint I have received - each PLM would
r
patch to 1.3 attached
On 7/30/08, Lenny Verkhovsky wrote:
>
> few more details:
>
> 1. added new mca param rmaps_base_slot_list (r19062)
>
> 2. new -slot-list option to mpirun ( r19062)
>
> 3. old opal_paffinity_base_slot_list will be invisible ( r19096)
>
> 4. few bug fixes ( r19
few more details:
1. added new mca param rmaps_base_slot_list (r19062)
2. new -slot-list option to mpirun ( r19062)
3. old opal_paffinity_base_slot_list will be invisible ( r19096)
4. few bug fixes ( r19004)
On 7/30/08, Lenny Verkhovsky wrote:
>
> if there is no objection I wa
if there is no objection I want to bring it to 1.3
( r19062)
On 7/28/08, Ralph Castain wrote:
>
> Just an FYI for those of you working with slot_lists.
>
> Lenny, Jeff and I have changed the mca param associated with how you
> specify the slot list you want the rank_file mapper to use. This was
FYI, I made a new trac report just for the v1.3 tickets so that we can
all look at the same screens on the Tuesday teleconferences:
https://svn.open-mpi.org/trac/ompi/report/14
This report is linked/listed as "Active tickets for v1.3" on the trac
reports page, and is linked to from the v
You're right, these defines are now useless. I remove them with the
commit 19091. Thanks for noticing.
george.
On Jul 29, 2008, at 2:43 AM, Jeff Squyres wrote:
Since the trunk has now been bumped to MCA v2.0, and all frameworks
have also been bumped to v2.0, are these two #defines relevan
