Ralph Castain ea0c03fd7a Revert out r14910. Turns out that the GPR *has* to be able to deal with NULL data values. We fixed this a long time ago on the "put" side, but never dealt with it for "get" - hence, we could "put" ORTE_UNDEF'd attributes in a mapping policy, but couldn't retrieve them. This is why you only encountered the error on comm_spawn and not during the original launch of a job. ... This correctly repairs the problem by enabling the GPR's "get" function to correctly handle NULL data values. This commit was SVN r14916. The following SVN revision numbers were found above: r14910 --> open-mpi/ompi@0757467d77		2007-06-06 18:34:54 +00:00
..
base	Revert out r14910. Turns out that the GPR *has* to be able to deal with NULL data values. We fixed this a long time ago on the "put" side, but never dealt with it for "get" - hence, we could "put" ORTE_UNDEF'd attributes in a mapping policy, but couldn't retrieve them. This is why you only encountered the error on comm_spawn and not during the original launch of a job.	2007-06-06 18:34:54 +00:00
round_robin	Compute and pass the local_rank and local number of procs (in that proc's job) on the node.	2007-05-21 14:30:10 +00:00
Makefile.am	Fix a bunch of install locations for header files	2005-12-08 00:54:44 +00:00
rmaps_types.h	Compute and pass the local_rank and local number of procs (in that proc's job) on the node.	2007-05-21 14:30:10 +00:00
rmaps.h	This doesn't totally resolve the comm_spawn problem, but it helps a little. I'll continue working on it and hope to resolve it completely shortly. The issue primarily centers on where to start mapping the child job's processes, and how to deal with oversubscription that might result. At the moment, I am trying to resolve the first issue first (hey, that even sounds right!).	2006-10-18 14:01:44 +00:00