Re: [MTT users] Tests build, but do not run

2006-10-13 Thread Ethan Mallove
On Thu, Oct/12/2006 03:01:53PM, Jeff Squyres wrote: > On Oct 11, 2006, at 11:34 AM, Ethan Mallove wrote: > > >So if I do put the four combinations of platform/bitness in > >a single ini file, I then have to do some ugly ini param > >overriding to line up the sections, e.g.,: > > > >Command 1) > >

Re: [MTT users] Tests build, but do not run

2006-10-13 Thread Jeff Squyres
On Oct 12, 2006, at 7:38 PM, Ethan Mallove wrote: [Test get: intel all] suite_name = intel [Test build: intel sparc 32] suite_name = intel [Test build: intel sparc 64] suite_name = intel [Test build: intel i386 32] suite_name = intel [Test build: intel i386 64] suite_name = intel [Test run: inte

Re: [MTT users] Tests build, but do not run

2006-10-12 Thread Jeff Squyres
On Oct 11, 2006, at 11:34 AM, Ethan Mallove wrote: So if I do put the four combinations of platform/bitness in a single ini file, I then have to do some ugly ini param overriding to line up the sections, e.g.,: Command 1) $ cat /home/em162155/mtt/all.ini | client/mtt -p -d - [...]

Re: [MTT users] Tests build, but do not run

2006-10-11 Thread Ethan Mallove
On Tue, Oct/10/2006 10:35:22PM, Jeff Squyres wrote: > I'm not quite sure I understand the problem. In each phase's section, you > are supposed to identify the one (or more) predecessor phase sections. For > example, in MPI install phases, you specify an "mpi_get" field that > indicates which MPI

Re: [MTT users] Tests build, but do not run

2006-10-11 Thread Jeff Squyres
I'm not quite sure I understand the problem. In each phase's section, you are supposed to identify the one (or more) predecessor phase sections. For example, in MPI install phases, you specify an "mpi_get" field that indicates which MPI get phases should be built with this install section: [MPI

Re: [MTT users] Tests build, but do not run

2006-10-09 Thread Ethan Mallove
To answer my own question, apparently Test Get/Build/Run section labels must indeed match up (http://svn.open-mpi.org/trac/mtt/wiki/MTTOverview). To work within these confines, I am instead breaking up my ini file into several ini files (see below), and have created a wrapper script to cat in only

[MTT users] Tests build, but do not run

2006-10-09 Thread Ethan Mallove
My intel tests compile okay, but then do not run. Here's the salient --debug output: ... >> Test build [test build: intel sparc 32] Evaluating: intel Building for [ompi-nightly-v1.2] / [1.2a1r12050] / [solaris sparc 32] / [intel sparc 32] Evaluating: Intel_OMPI_Tests Making dir: tests (cwd: /wo