We moved a few fixes and improvements over to the MTT release branch
yesterday; you probably want to run "svn up" in your MTT checkouts.
I also added a "tips and tricks" section to the wiki on the OMPI Testing
page for some of the gotchas that have occurred so far.
Indeed, we'll be carefully
On 8/29/06 8:57 PM, "Josh Hursey" wrote:
>> Does this apply to *all* tests, or only some of the tests (like
>> allgather)?
>
> All of the tests: Trivial and ibm. They all timeout :(
Blah. The trivial tests are simply "hello world", so they should take just
about no time
FYI -- see:
This means that MTT will potentially have to test less stuff. More
specifically, MTT will only have a tarball to test when there is actually
something new to test. Hence, this can significantly decrease the
proability of their being 1.1 and 1.0 tarballs to test, and therefore
I'm trying to replicate the MTT environment as much as possible, and
have a couple of questions.
Assume there is no mpirun in my PATH/LD_LIBRARY_PATH when I start
MTT. After MTT builds Open MPI, how does it export these variables so
that it can build the tests? How does it export these
FWIW, I am pretty sure that "srun -b myscript" *used* to work.
But there must be something different about the environment between the two
(-A and -b)...? For one thing, mpirun is running on the first node of the
allocation with -b (vs. The head node for -A), but I wouldn't think that
that would
On Aug 30, 2006, at 11:36 AM, Jeff Squyres wrote:
(sorry -- been afk much of this morning)
MTT directly sets environment variables in its own environment (via
$ENV{whatever} = "foo") before using fork/exec to launch compiles
and runs.
Hence, the forked children inherit the environment
This fixes the hanging and gets me running (and passing) some/most of
the tests [Trivial and ibm]. Yay!
I have a 16 processor job running on Odin at the moment that seems to
be going well so far.
Thanks for your help.
Want me to file a bug about the tcsh problem below?
-- Josh
On Aug
Josh noticed that Test Run data is not currently being recorded. I actually
had already filed ticket #42 about this -- just to let you all know, we're
aware of the problem and Ethan is working on it.
Also, I just brought over the CSH script fix that Josh identified earlier
(i.e., the sourceable