Add "fast" mode to run_remote_tests which causes the user to no longer need to emerge autotests before running them (even ones that require compilation.)
Change-Id: I60c1e8bfe562a787075b4f65b714e221e51934f7
BUG=8784
TEST=Ran bvts in and out of fast mode, ran UserCrash, SanAngeles, TPM, and backlight tests (which require compilation) in fast mode.
Review URL: http://codereview.chromium.org/4020004
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
Change-Id: If83bf22fde6259b64fdd007066b5c46c7925d120
BUG=
TEST=Run a few tests inside and outside chroot
Review URL: http://codereview.chromium.org/3790005
Autotest will not split comma separated arguments. The correct calling method for multiple arguments is to separate them by spaces and quote the whole thing. E.g., instead of:
./run_remote_tests --args arg1,arg2
It should be:
./run_remote_tests --args "arg1 arg2"
See line 140 in src/third_party/autotest/files/server/autoserv_parser.py for
confirmation.
Change-Id: I88d65c0bd144942a856c2f95371d5a55b0a3a172
BUG=
TEST=No code changes. Ran --help and --args to verify nothing dumb happened and the correctness of comment.
Review URL: http://codereview.chromium.org/3772002
1) image_to_vm aborts because e2fschk requires a terminal to
be connected in order to check whether or not you want to repair the fs. Since
we always want this to be true, set -p
2) Clean up test harness to only verify the number of tests that passed on the
base image are the same on the update back to. This is because older images
have many tests that fail. I leave 10% as a reasonable number to pass.
3) Redirect output from autotest in run_remote_tests to stderr so it gets
logged in a calling script that captures stdout.
Change-Id: If412274353683add20d136747113eb9c2bd41330
BUG=4690, 5533, 7287
TEST=Ran with internal tools for builders.
Review URL: http://codereview.chromium.org/3536018
Change-Id: I1ad0aaec6517758812bf4ba0460ab0c81a6f84cb
BUG=7357
TEST=run_remote_tests.sh ... bvt regression and then observer both bvt and regression test result
Review URL: http://codereview.chromium.org/3603012
BUG=5817
TEST=run_remote_tests --remote=$IP control shows ^...$ on all lines.
Change-Id: Ie0c4ac16493dc97044ec0bd0fd6d6e53a69c9041
Review URL: http://codereview.chromium.org/3473015
Change-Id: I8560a4400463d04b7a2441ce6fa9dc9cec834242
BUG=
TEST=run_remote_tests.sh --args='-n 10', and make sure it gets all the way into autotest_run.sh
Review URL: http://codereview.chromium.org/3402007
* stops the second-pass parsing of arguments into IFS-delimited elements
which unbreaks things like --args='-n 10'
Change-Id: If8424b5fc06e6dd5a935421a76539e7e91006c37
BUG=
TEST=run it and see the argument being passed correctly
Review URL: http://codereview.chromium.org/3422005
Change-Id: I664858ff9b931479fe2fac89a24aa3e7fce8493b
BUG=
TEST=ran rrt without ==board or default board set
Review URL: http://codereview.chromium.org/3431004
* Fixes running tests different than from the main autotest repo
* Also provides a better fix for chrome tests
Change-Id: I803ba7caa5561e3001d5627219718f471e59bb19
BUG=
TEST=
Review URL: http://codereview.chromium.org/3448002
BUG=4887
TEST=tested run_remote_tests and image_to_live still work. Ran script with machine with no crashes, as well as on a machine with a slew of powerd CHECK(false)'s.
Change-Id: Iffb6571d30d99d876f41972f92a7149a716035ee
Review URL: http://codereview.chromium.org/3276002
Change-Id: I758c93596d5cbdd6b52b9acc82f4d6e19a326c9f
BUG=5518
TEST=Tested using all the options. All tests listed in the file pass.
Review URL: http://codereview.chromium.org/3107039
* Also changes the way how "new workflow" is detected in run_remote_tests.sh
modified: autotest_run.sh
modified: run_remote_tests.sh
Review URL: http://codereview.chromium.org/3048051
* This script should replace the call to ebuild in autotest wrapper, and essentially
duplicates all the test running functions from autotest-0.0.1.ebuild
* duplicate autotest wrapper into autotest_workon to separate conversion and old functionality
* Add a hack into run_remote_tests to allow using autotest_workon instead
new file: autotest_run.sh
new file: autotest_workon
modified: run_remote_tests.sh
Review URL: http://codereview.chromium.org/2854062
Make this script's output better formatted. Better describe how
to disambiguate control files when multiple match. Get rid of
the output_file concept since it's not needed. Don't output
a results directory if there's an ambiguity.
Review URL: http://codereview.chromium.org/1090005
sync_build_test runs build_autotest that way.
archive_build bzips up the autotest artifacts.
run_remote_tests can run autotest artifacts from a prepackaged directory. Note that because build_platform is in a different repository than these other files, it's unfortunately forced to be reviewed separately in http://codereview.chromium.org/661197 and committed independently.
Review URL: http://codereview.chromium.org/660189
this is necessary for portage-based builds which change the
chroot. You must pass --chroot to the run_remote_tests in this
case.
Review URL: http://codereview.chromium.org/588010
Don't punish the good people trying to write python-only autotests by
requiring them to sit through a long build_autotest run to test
every change. run_remote_tests and build_autotest both update
the chroot copy now.
Review URL: http://codereview.chromium.org/578027
Run a basic check on a buildbot grabbed image to make sure it has a
kernel installed in it.
Better failure recovery.
Review URL: http://codereview.chromium.org/553063
image_to_live.sh - fix problem where errorvalue is non-zero even when
reimage was successful.
run_remote_tests.sh - add ability to stow build description in the
autotest database so we can track the exact build for which
tests succeed/fail.
Review URL: http://codereview.chromium.org/547018
This is a script to run client or server autotests on a live Chromium OS instance, collect results, and optionally upload the to an autotest database. This includes functional and performance tests. We assume the remote instance is running an appropriate image installed (one created using mod_image_for_test.sh and possibly installed using image_to_live.sh).
An example run might be
run_remote_tests.sh --remote=192.168.1.5 BootPerfServer -o results.txt
This example will run src/platform/testing/server_tests/system_BootPerfServer
5 times on instance at 192.168.1.5 and collect results in result.txt.
Also refactors and improves readability in image_to_live.sh.
Review URL: http://codereview.chromium.org/519041
