On Wed, 16 Jul 2003, jeremy archuleta wrote:
> If you believe that this is important, I will submit all the files
> required when reporting an error. Otherwise... it's off to the beach.
Short version -- go to the beach! :-)
Longer version:
The sysv RPI tries to allocate a number of OS-level semaphores and shared
memory descriptors, and is directly proportional to the number of MPI
processes that are launched on a given machine. If you launch enough
processes on a single machine such that the sysv RPI is unable to get
enough semaphores/shared memory, it will abort.
The test cases that you cite run a fixed number of processes (6 or 8)
rather than across your current universe ("C") because of the nature of
the specific functionality that they're trying to test. sysv can't
allocate enough resources in these cases, so it aborts the tests.
This is safe to ignore because the functions that are being tested are
simply exercises in data structure management -- there's little or no
communication involved that isn't already tested in all the other
lamtests.
I see that we didn't mention this in the docs about the test suite in the
Installation Guide; a problem that I'll fix for 7.1. :-)
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
