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) > > > >$ cat /home/em162155/mtt/all.ini | > > client/mtt -p -d - > > [...] > > mpi_get='ompi-nightly-trunk' > > "intel:test_build='intel $arch $bit'" > > "imb:test_build='imb $arch $bit'" > > "ibm:test_build='ibm $arch $bit'" > > "trivial:test_build='trivial $arch $bit'" > > > >I was thinking it would be nice if I could do something > >like this in my ini: > > > >[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: intel all] > >suite_name = intel > > Why do you need different test build sections? >
Different intel_ompi_tests_(f|c)flags parameters for each. -Ethan > -- > Jeff Squyres > Server Virtualization Business Unit > Cisco Systems >