For the 1.0 test harness release we are including a full application
suite, MIMD Lattice Computation (MILC). This version, milc_v7, was obtained
from the website physics.utah.edu at the University of Utah. None of the
code was modified, although we copied the file Make_test_all to makefile in
order to more easily facilitate the default name of the make file within
the test harness. We also modified the result verification code with the
file diffn3.pl to print out "PASSES" and "FAILS" instead of "OK" and
"NOT OK", also to just make it easier to fit into existing database entries
already marked for success runs.

Note that since milc tests require libraries and other referenced files to
build its executables we use the -copysrc option to runtest. This option 
will copy the source tree from the directory containing the make file to
the temporary working directory instead of just the make file. The 
suitetype for this test is Applications and the suite is milc_v7. The
command:
   runtest -suite milc -test clover_dynamical -copysrc
will run just the clover_dynamical test, while
   runtest -suite milc -copysrc
will run all the tests within milc. For reference,
   runtest -suite milc_v7 -compiler gcc -copysrc
will run the milc tests using the gcc compiler.


Also note that the default compiler for milc is pgcc. This value is set in
the database table suite, under the compilerid column. It can changed 
permanently by updated the field entry in the database table, or can be
change temporarily by using the "-compiler" option to runtest.

Regarding timings: the runtest infrastructure will keep track of total time
as well as execution time. These values are displayed on the web page in
the test log header. Although some minor overhead is included in total time
(copying sources, changing directories, etc.) a good indication of compile
time can extracted by using the value total time minus execution time.

If the system running milc is not particuarly fast, some of the tests (in
particular ks_imp_rhmc) may exceed the default timeout of 600 seconds. If
that occurs try setting the column timeout value in the database table 
to 2 or 3. This value is a multiplier of the default suite executable timeout 
value (600 in this case). One could also change the default suite etimeout
by entering a value within the suite (milc_v7) database table.
