On my trunk MTT runs, I'm getting a bunch of timed out tests with this message:
[node014][[56709,1],31][btl_tcp_endpoint.c:678:mca_btl_tcp_endpoint_complete_connect] connect() to 10.1.0.7 failed: No route to host (113) This appeared to be due to a problem with a switch in my cluster, but the larger problem is that all the tests then *hung*. Is this intentional? -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/