MTT was designed to be able to be interrupted; if you re-start MTT with the same command line arguments and ini file and nothing has changed on the server side (e.g., no new version of MPI or version of tests), MTT should resume where it left off.
However, in some cases, results for all the tests won't be reported. For example, if you interrupt MTT in the middle of a long intel test run, although MTT has all the meta data for the tests that have already been run (and will properly resume where it left off if you restart MTT), it will only report the results of the tests that it executed during the current run. That is, the results of the tests of the previous run are not reported back to the database.
MTT was designed to be able to be interrupted; if you re-start MTT with the same command line arguments and ini file and nothing has changed on the server side (e.g., no new version of MPI or version of tests), MTT should resume where it left off.
However, in some cases, results for all the tests won't be reported. For example, if you interrupt MTT in the middle of a long intel test run, although MTT has all the meta data for the tests that have already been run (and will properly resume where it left off if you restart MTT), it will only report the results of the tests that it executed during the current run. That is, the results of the tests of the previous run are not reported back to the database.