You might want to put a little more debug diag output in those code paths and run the test manually to see what's up. Sorry I don't have a better idea offhand. :-(
On Apr 16, 2010, at 11:24 AM, Ethan Mallove wrote: > I've filed a Trac ticket for this issue: > > http://svn.open-mpi.org/trac/mtt/ticket/393 > > On Wed, Apr/14/2010 11:36:04AM, Jeff Squyres wrote: > > That's interesting -- I see "Failed; exit status: 0" in the "Result > > message" field. > > > > Looks like that's coming from Test::Analyze::Correctness. Somehow $pass > > came out to be 0, so it fell into the "fail" path...? > > > > > > On Apr 14, 2010, at 10:51 AM, Ethan Mallove wrote: > > > > > This loop_spawn test appears to have passed, though it's marked > > > as FAIL: > > > > > > http://www.open-mpi.org/mtt/index.php?do_redir=1233 > > > > > > Its pass condition is set to: > > > > > > pass = &and(&test_wifexited(), &eq(&test_wexitstatus(), 0)) > > > > > > -Ethan > > > _______________________________________________ > > > mtt-users mailing list > > > mtt-us...@open-mpi.org > > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > > > > > > > > > -- > > Jeff Squyres > > jsquy...@cisco.com > > For corporate legal information go to: > > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > > > > _______________________________________________ > > mtt-users mailing list > > mtt-us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > _______________________________________________ > mtt-users mailing list > mtt-us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users > -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
