This harkens back to some discussions of being able to see the available
results of an incomplete MTT run. Currently, for any given INI file, MTT will
do:
Every MPI Install
Every Test Build
Every Test Run
Sometimes it would be preferable for MTT to do, e.g.,
Every MPI Install
Test Build and Test Run for the Intel tests
Test Build and Test Run for IMB tests
etc.
How about this?
{{{--order [phase|suite]}}} (Default to the usual {{{phase}}}.)
''Note: a work around is to have separate INI files for each of the above stages,
e.g.,''
''So that mtt will run all the available phases listed in each INI file. The above command will have a different order of execution than the following, which executes the concatenation of all the INI files as if it were an individual INI file:''
This harkens back to some discussions of being able to see the available results of an incomplete MTT run. Currently, for any given INI file, MTT will do:
Sometimes it would be preferable for MTT to do, e.g.,
How about this?
{{{--order [phase|suite]}}} (Default to the usual {{{phase}}}.)
''Note: a work around is to have separate INI files for each of the above stages, e.g.,''
{{{mtt --file "installs.ini intel.ini imb.ini ..."}}}
''So that mtt will run all the available phases listed in each INI file. The above command will have a different order of execution than the following, which executes the concatenation of all the INI files as if it were an individual INI file:''
{{{cat installs.ini intel.ini imb.ini | mtt -}}}