On Mon, Feb 4, 2013 at 8:45 PM, Jeff Squyres (jsquyres)
wrote:
> That will still be quite difficult to do in MTT. Remember: all the tests
> that are run in MTT are shared across all of us via the ompi-tests SVN repo.
> Are you suggesting that I alias every test in the ompi-tests SVN with a
>
On Feb 4, 2013, at 2:03 PM, George Bosilca wrote:
> The two behaviors you describe for include and exclude do not look
> conflicting to me. Inclusion is a strong request, the user enforce the usage
> of a specific interface. If the interface is not available, then we have a
> problem. Exclude
If it ain't broke, don't fix it. I am more than skeptical about the
interest of this new notation.
The two behaviors you describe for include and exclude do not look
conflicting to me. Inclusion is a strong request, the user enforce the
usage of a specific interface. If the interface is not availa
On Feb 1, 2013, at 9:59 PM, "Barrett, Brian W" wrote:
> I don't think this is right either. Excluding a device that doesn't exist has
> many use cases. Such as disabling a network that only exists on part of the
> cluster. I'm not sure about what to do with seq; it's more like include than
>
On Feb 1, 2013, at 7:09 PM, George Bosilca wrote:
> I did not say we abort, I say we prevent BTL TCP from being used.
Ah.
> In your example, I guess the TCP is disabled but the PML finds another
> available interface and keeps going. If I try the same thing with
> "--mca btl tcp,self" it does a
I did not say we abort, I say we prevent BTL TCP from being used. In
your example, I guess the TCP is disabled but the PML finds another
available interface and keeps going. If I try the same thing with
"--mca btl tcp,self" it does abort on my cluster.
---
mpirun -np 2 --mca btl tcp,self --mca btl
On Feb 1, 2013, at 6:28 PM, George Bosilca wrote:
> So far, all interfaces specified via MCA parameters for the BTL TCP
> are required to exist. Otherwise an error message is printed and an
> error returned to the upper level, with the intent that no BTLs of
> this type will be enabled (as an exa
Jeff,
So far, all interfaces specified via MCA parameters for the BTL TCP
are required to exist. Otherwise an error message is printed and an
error returned to the upper level, with the intent that no BTLs of
this type will be enabled (as an example btl_tcp_component.c:682).
If I correctly unders
