Hi all,
I have problems with the openmpi-default-hostfile since the following
patch on the trunk
changeset: 19874:088fc6c84a9f
user:rhc
date:Wed Feb 01 17:40:44 2012 +
summary: In accordance with prior releases, we are supposed to default
to looking at the openmpi-defa
That's strange - I run on slurm frequently and never have this problem, and my
default hostfile is present and empty. Do you have anything in your default mca
param file that might be telling us to use the hostfile?
The only way I can find to get that behavior is if your default mca param file
Sorry folks -- I hadn't noticed that several pending 1.5 CMRs hadn't been
rolled in yet. I'll ping George.
On Feb 26, 2012, at 5:42 PM, Paul Hargrove wrote:
>
>
> On Sun, Feb 26, 2012 at 6:37 AM, Ralph Castain wrote:
> [snip]
> In the example you gave, the library you were adding ("dummy mt
Testing 1.5.5rc2, I see warnings about an unknown IB HCA unless I make
the following simple addition:
--- ompi-v1.5/ompi/mca/btl/openib/mca-btl-openib-device-params.ini
(revision 26056)
+++ ompi-v1.5/ompi/mca/btl/openib/mca-btl-openib-device-params.ini
(working copy)
@@ -127,7 +127,
In the test suite, we have an ibm/dynamic/loop_spawn test that looks
like this:
for (...) {
loop_spawn spawns loop_child
parent and child execute MPI_Intercomm_merge
parent and child execute MPI_Comm_free
parent and child execute MPI_Comm_disconnect
}
If
I believe that's the subject of several tickets…
On Feb 27, 2012, at 8:24 PM, Eugene Loh wrote:
> In the test suite, we have an ibm/dynamic/loop_spawn test that looks like
> this:
>
>for (...) {
>loop_spawn spawns loop_child
>parent and child execute MPI_Intercomm_merge
>
