| 03ad6fa7b8520611f3687890210c38532112208a |
|
22-May-2014 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: handle exceptions when creating .version file
When running the version.sh script to create and scp the .version
file to the remote machine, it may fail sometimes. I conjecture
that when performing scp, there are many situations that may arise,
including the issues associated with accessing .ssh/known_hosts,
network may timeout, network may lose connection for whatever
reasons, etc.
This patch adds more exceptions handling in the expect_scp script,
and prints the error messages to stderr to ensure that the error
messages could be included in the output log when executing
run_remote_tests.sh. Besides, the flags StrictHostKeyChecking=no
and UserKnownHostsFile="/tmp/null" are added to scp command to
reduce the unnecessary warning/error messages.
BUG=chromium:375374
TEST=Setup the autotest from chroot, and make sure all tests PASSED
in various platforms.
(cr) run_remote_tests.sh --autotest_dir ~/trunk/src/third_party/autotest/files
--remote=$MACHINE_IP firmware_TouchMTBSetup
Change-Id: Ica650f50ef4e3b6c186eaf5e7e472f998bd2c9d2
Reviewed-on: https://chromium-review.googlesource.com/201061
Reviewed-by: Charles Mooney <charliemooney@chromium.org>
Tested-by: Charles Mooney <charliemooney@chromium.org>
Commit-Queue: Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/version.sh
|
| 4a0a07b966ca63c9c3c0d258f7e2fc1468050ebe |
|
10-Mar-2014 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: Use a full path and expect_scp
Since a server test is possible to invoke this script from an unknown
path, a full path needs to be employed instead of a relative path.
In addition, use expect_scp to automate scp without user interaction.
BUG=chromium:315787
TEST=None. Will be tested later.
Change-Id: I5be7950fe6ab3c3fd97f0b12f65995288c262e4b
Reviewed-on: https://chromium-review.googlesource.com/189461
Reviewed-by: Shyh-In Hwang <josephsih@chromium.org>
Commit-Queue: Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/version.sh
|
| 5db2d13bf7ff0e56c652213434f581ce6d7a65ee |
|
11-Feb-2014 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: create the version info and scp it to test machine
It is helpful to add version information in the test results so that
we know the version of the test suite that generates the results.
In this patch, a script is provided to generate the version
information and scp it to the test machine. In next patch, there
should be some automatic way to invoke the script. For example,
add a hook in test_that script which will replace run_remote_tests.sh
BUG=chromium:315787
TEST=Perform the steps in chroot
(cr) $ cd .../site_tests/firmware_TouchMTB
(cr) $ ./test_that_hook.sh -r ${CHROMEBOOK_IP_ADDRESS}
As an example:
(cr) $ ./test_that_hook.sh -r 100.20.300.123
On the chromebook machine,
$ cat /usr/local/autotest/tests/firmware_TouchMTB/.version
It should print something like
version: 2014-01-23.16:18:24 1feddb865cf3f9c158d8cca17a6e68c71b500571
Change-Id: I652c0aa7e7c3ec6f42904cdfc21a8905896fc9ab
Reviewed-on: https://chromium-review.googlesource.com/185816
Reviewed-by: Charles Mooney <charliemooney@chromium.org>
Commit-Queue: Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/version.sh
|