4 Commits

Author	SHA1	Message	Date
Darin Petkov	c0644eb90a	VM: Implement --order_output option in cros_run_parallel_vm_tests. ... If the option is specified, the utility will pipe the test stdout/stderr to separate files and dump them at the end. BUG=8585 TEST=./bin/cros_run_parallel_vm_tests suite_Smoke suite_Smoke --order_output Change-Id: I6c4fcb02456441b4e4fc3f1717cdb5d607d733b9 Review URL: http://codereview.chromium.org/4422001	2010-11-03 14:53:18 -07:00
Darin Petkov	40508146b3	VM: Add board, image_path and base_ssh_port options. ... BUG=8585 TEST=manual, tried different options Change-Id: I66be3930cefdf4ea382e1ed8aba54a66f4bfb36e Review URL: http://codereview.chromium.org/4403001	2010-11-03 12:47:15 -07:00
Darin Petkov	3bab032123	VM: Add --results_dir_root option to cros_run_parallel_vm_tests ... This allows the user to specify a custom results directory root. cbuildbot can be switched to use cros_run_parallel_vm_tests if necessary without any further changes. Also create parents directories for user-specified results directory roots in run_remote_tests. BUG=8585 TEST=./bin/cros_run_parallel_vm_tests suite_Smoke suite_Smoke \ --results_dir_root=/tmp/foo Change-Id: I7314c1d9e74ca139eaa4bd95290866a43a3606ff Review URL: http://codereview.chromium.org/4297003	2010-11-03 11:20:53 -07:00
Darin Petkov	a424d94ab3	A basic utility to allow running of tests on VMs in parallel. ... Current usage is simple: just specify a list of tests and each one will be run on a separate VM using the latest image on a default board. Exit code is non-zero if any of the tests fail. Output from separate tests is interleaved. More CLs to follow -- specifying a result directory, non-interleaved output, base ssh port, board, image path, etc. BUG=8585 TEST=./bin/cros_run_parallel_vm_tests suite_Smoke suite_Smoke Change-Id: Ifa3396768050905ec02e4cad8b8f065a6d129154 Review URL: http://codereview.chromium.org/4337003	2010-11-03 10:09:39 -07:00