On Oct 18, 2008, at 12:46 AM, Steven wrote:
> Thanks for your answer. My server has openmpi installed.
Ah -- since you mailed the LAM list, I assumed that you were asking
about using the test suite with LAM/MPI. If this is actually an Open
MPI question, we should move this thread to the Open MPI devel mailing
list.
I'll reply in more detail there (see http://www.open-mpi.org/community/lists/users/)
.
> I also know MTT for testing openmpi. But my cluster has no access to
> internet. So I have to use lamtest.
> If you have any advice, that would be greatly appreciated.
>
> Thanks again.
>
> Steven Wang
>
> ÔÚ2008-10-17£¬"Jeff Squyres" <jsquyres_at_[hidden]> дµÀ£º
> >LAM does not know anything about udapl, so I'm not sure how you could
> >be generating these messages unless you are somehow mixing MPI
> >implementations (perhaps mixing Open MPI and LAM/MPI somehow? Even
> >so; Open MPI doesn't build udapl by default on Linux because it
> >prefers native verbs support).
> >
> >Note that the "make check" mechanism in the Open MPI SVN version of
> >the ibm test suite is not used much; it may or may not be 100%
> >functional (i.e., it may have bit rotted over time). I typically use
> >the MPI Testing Tool (MTT) to run all the IBM tests; MTT is much more
> >reliable and flexible. MTT finds all the executables that were
> >generated by "make" and runs them by itself, not via "make check".
> >For example, here's Cisco's Open MPI testing results from the IBM
> test
> >suite from yesterday:
> >
> > http://www.open-mpi.org/mtt/index.php?do_redir=868
> >
> >
> >
> >On Oct 17, 2008, at 3:55 AM, Steven wrote:
> >
> >> Hi Tim and Jeff:
> >>
> >> You are right that I combined some *.o files into my compiling
> >> server. These objective files were compiled on differnt enviroment,
> >> which resulted in the issue. I removed them and rerun make. This
> >> time make or make -k is clear. When I run "make -k check", the
> >> output has continous warning such as
> >>
> >> WARNING: Failed to open
> >> "ib0" [DAT_PROVIDER_NOT_FOUND:DAT_NAME_NOT_REGISTERED].
> >> This may be a real error or it may be an invalid entry in the uDAPL
> >> Registry which is contained in the dat.conf file. Contact your
> local
> >> System Administrator to confirm the availability of the
> interfaces in
> >> the dat.conf file.
> >>
> >> My servers have one Infiniband ConnectX adapter connected. It looks
> >> that lamtest will detect the IB network. At the output end of
> "make -
> >> k check", it wrote
> >>
> >> PASS: sub
> >> ==================
> >> All 4 tests passed
> >>
> >> I am not sure how many test cases have been executed (only four
> >> cases?). And whether 100% of them has succeeded or not.
> >>
> >> Thanks a lot for your attetion!
> >>
> >> Steven Wang
> >> ÔÚ2008-10-16£¬"Tim Prince"
>
>
> [¹ã¸æ] ½ðÇï×î¹Øע¥ÅÌ-·¿²»Ê¤·¿
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
--
Jeff Squyres
Cisco Systems
|
