| commit | 53558128ecfc6e36bb61cab5e40ac54d66b98ef6 | [log] [tgz] |
|---|---|---|
| author | Dan Shi <dshi@google.com> | Sat May 07 11:09:22 2016 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue May 10 19:42:03 2016 -0700 |
| tree | d341933fc5411fb2902a0168453a1769518a8601 | |
| parent | 4aff0a87d4483f151b82dd8c37081083338871b7 [diff] |
[autotest] Raise DevServerException if devserver response contains error.
When global config enable_ssh_connection_for_devserver is set to True, devserver
calls are made by ssh to devserver and run a curl command to devserver request.
If the devserver request failed, the curl command won't return a
urllib2.HTTPError, instead, it just returns the string of the HTTP response.
Without that error, client will repeatedly make the request until timeout, which
misleads user to think devserver has some issue.
This change checks the HTTP response to see if there is any certain string of
exception raised by devserver. It's the most reliable way but the only thing
available for now.
BUG=b:28643167
TEST=local run
set enable_ssh_connection_for_devserver to True
Try to make some devserver call that known will fail, e.g.,
import common
from autotest_lib.client.common_lib.cros import dev_server
build_info = {'branch': 'git_mnc-release',
'target': 'shamu-userdebug',
'build_id': '2419303', 'os_type': 'android'}
build_name = '%(branch)s/%(target)s/%(build_id)s' % build_info
devserver = dev_server.AndroidBuildServer.resolve(build_name, 'localhost')
devserver.stage_artifacts(build_info['target'], build_info['build_id'],
build_info['branch'],
artifacts=['none_existing_package'])
Change-Id: I53faf12182a67085bf331976eb90267a6dc54b34
Reviewed-on: https://chromium-review.googlesource.com/343291
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>
Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.
Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:
A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.
A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.
Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.
Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.
Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.
See the guides to test_that and test_droid:
See the best practices guide, existing tests, and comments in the code.
git clone https://chromium.googlesource.com/chromiumos/third_party/autotest
See the coding style guide for guidance on submitting patches.