All --

I re-factored some of the code today to [finally] split out the test source stuff into a new phase named "test get" (analogous to the "mpi get" phase). This allowed for some nice code consolidation in some places, and more importantly, is another step towards supporting disconnected scenarios.

See samples/sample.ini for some examples of the [Test get:] phase. The point is that you can specify where the test suite sources are located and they get downloaded once and cached (just like the MPI sources). This phase also has its own command line switch on the "mtt" client ("--get-test").

Previously, we mixed both obtaining the test suites and building the test suites in the "test build" phase. Now they're properly split apart into two phases. So if you have old .ini files, you can generally create new [test get:] sections with the sources from your [test build:] sections and it'll be ok. See sample.ini for examples.

I unfortunately just realized that I did the linkage from the "test get" phase to the next phase ("test build") entirely wrong. :-(

So if you're trying to build or run any tests with the SVN head, it just won't work. You might want to roll back to before my big commit from this afternoon (r158 should be safe). I'll fix the head either later tonight or tomorrow morning. Sorry folks...

And crud, as I was typing out this mail, I realized that the mtt command line options are the opposite wording of the INI file phase names (e.g., "[MPI install:]" vs. --install-mpi). Tomorrow, I'm going to change the mtt command line options to be the other way around (--mpi-get, --mpi-install, --test-get, ...etc.). Blah!

--
{+} Jeff Squyres
{+} The Open MPI Project
{+} http://www.open-mpi.org/


Reply via email to