#4 Support running tests on remote machines

[Ian Hinder]

Notes:

• We cannot log in to remote machines from an unattended process for security reasons. Hence we must set up some sort of polling process on the remote machine (e.g. via cron or screen). This would poll a web server that we control and fetch a tarball of a source tree to test. This tarball would be regularly generated by us.
• Once the tarball is downloaded, it will be extracted and built using simfactory (i.e. the testsuites script will run on the remote machine, getting the code from this tarball rather than using GetComponents). It will use create-submit instead of create-run to run the tests in batch jobs. An independent polling process (running on the remote machine) will check periodically if there are new test results in the simulations directory, and if so, it will send these results to a server that we control.