8e6affb2614b6b6f03ab97b52740f03df1470ade |
|
16-Dec-2015 |
Simran Basi <sbasi@google.com> |
[autotest] Pass in --lab to autoserv for Special Tasks. Special tasks kick off autoserv in a number of different locations, this change informs special tasks ran by the scheduler that they are running in the lab. BUG=chromium:570125 TEST=Local MobLab run. Change-Id: I741f64a54bf5ce0997be34435ad7db1a2051e39d Reviewed-on: https://chromium-review.googlesource.com/318753 Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/server/autoserv_utils.py
|
14622bb8249c2200e5258ea6d40b3362229e90a7 |
|
25-Nov-2015 |
Simran Basi <sbasi@google.com> |
[autotest] test_droid V1. This CL introduces test_droid, a script to launch autotest tests against local Android DUTs connected to the host computer via USB. Much of the logic is similar to test_that, so this has all been pulled into a new script test_utils.py Pending work: * Moving of generate_test_report to somewhere it is accesible outside of the chroot. * Add in support for remote adb hosts (i.e. the DUT is connected to a remote computer). * Sequences support. BUG=b:25748759 TEST=./test_droid.py 7d52318 brillo_WhitelistedGtests CQ-DEPEND=CL:315230 Change-Id: Idab3805f7921173fbc706354b322f37244240fa2 Reviewed-on: https://chromium-review.googlesource.com/314870 Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/autoserv_utils.py
|
1bf60eb788365f083d0ee8045a6556f906149dec |
|
02-Dec-2015 |
Simran Basi <sbasi@google.com> |
[autotest] autoserv add --lab & --host_attributes arguments Added two new flags to autoserv. --lab indicates that autoserv is running in the lab and has the full Autotest infrastructure at its disposal. --host_attributes allows host attribute information that is usually in the database to be retrievable from the command line arguments. If --lab is pulled in, autoserv will request the host attributes from the database at test runtime. From here this change, then updates the concept of the "machines" list that test control files receive to now be a list of dicts that contain the machine hostname and host attributes. This will enable identifing information the hosts library needs to create host objects to be available whether or not there is a database present. BUG=chromium:564343 TEST=local autoserv runs. Also verified scheduler changes work via MobLab. waiting on trybot results. DEPLOY=scheduler Change-Id: I6021de11317e29e2e6c084d863405910c7d1a71d Reviewed-on: https://chromium-review.googlesource.com/315230 Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/server/autoserv_utils.py
|
b669cbdea7f4bfc9cbfcea48d9cf9ce62f0deff5 |
|
13-Sep-2013 |
Dan Shi <dshi@chromium.org> |
[autotest] Disable install autotest from job_repo_url for test_that use_packing option for autotest._install method is True by default. When using test_that to run test, DUT will try to install autotest package from job_repo_url with server configured in global_config (cautotest). For DUT not located in lab, there is no job_repo_url existed for such DUT in cautotest, and therefore autotest will try to copy over the local files. However, when a user try to use a DUT in the lab to run test_that, autotest package is downloaded and installed from job_repo_url. That leads to a problem that developers can't use test_that to verify autotest code. The fix is to add a new option no_use_packaging to autoserv, and thread the option to autotest._install. The option is set to False by default, and set to True in test_that. Also, when this argument is set to True, any package installation will use AutoservFetcher. BUG=chromium:265673 TEST=run following command and confirm local autotest code is copied over to the DUT: test_that -b lumpy 172.22.75.225 dummy_Pass Change-Id: I365f5f7dc79c8e65cddaa0af77f1f1a1e4b0012a Reviewed-on: https://chromium-review.googlesource.com/169343 Reviewed-by: Mungyung Ryu <mkryu@google.com> Commit-Queue: Mungyung Ryu <mkryu@google.com> Tested-by: Mungyung Ryu <mkryu@google.com>
/external/autotest/server/autoserv_utils.py
|
c330bee1a59b0c2bb385b79db43b49098b1ee55a |
|
22-Oct-2014 |
Fang Deng <fdeng@chromium.org> |
[autotest] Deprecate the use of site_parse Some digging through the git history shows that site_parse was introduced to generate a json file about the test results and crash reports, which was later included in an email sent out by the old dashboard (see crbug.com/196118). Since we've completedly deprecated the old dashboard (crosreview.com/220690), there is no point to call site_parse any more. And since around Nov, 2013, we actually has stopped calling site_parser anyway because the import_site_function has been failing to load site_parser. Search scheduler logs you'll see tko/parser is called currently. So it won't harm to just remove the dead code that is trying to call site_parser. This will also simplify the measuring of duration of parsing (no need to take care of site_parser) BUG=chromium:422581 TEST=run scheduler locally. run run_suite. DEPLOY=scheduler Change-Id: I2232f245ab9e532c18bce723fb559617e6dab121 Reviewed-on: https://chromium-review.googlesource.com/224844 Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Fang Deng <fdeng@chromium.org> Tested-by: Fang Deng <fdeng@chromium.org>
/external/autotest/server/autoserv_utils.py
|
5e2bb4aa28611aaacaa8798fd07943ede1df46c6 |
|
28-Oct-2013 |
beeps <beeps@chromium.org> |
[autotest] Scheduler refactor. Break scheduler into simpler modules. This change also modifies run_pylint to check for undefined variables. BUG=chromium:312338 TEST=Ran smoke suite against multiple duts. Triggered agents like repair, verify etc. Pylint, Unittests. DEPLOY=scheduler Change-Id: Ibd685a27b5b50abd26cdf2976ac4189c3e9acc0a Reviewed-on: https://chromium-review.googlesource.com/174080 Commit-Queue: Prashanth B <beeps@chromium.org> Tested-by: Prashanth B <beeps@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org>
/external/autotest/server/autoserv_utils.py
|
c5947faa755945f81537c6c33c322dccacac0ade |
|
04-Sep-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] add a --ssh_options option to autoserv This CL follows the template of https://chromium-review.googlesource.com/167415 BUG=chromium:285378 TEST=Unit tests pass. Manually verified that specifying --ssh_options="-F /dev/null -i /dev/null" caused those flags to be threaded into ssh commands. Change-Id: Ie0496862d05d42192d55501fc0ed1c3a6274fe79 Reviewed-on: https://chromium-review.googlesource.com/168099 Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/autoserv_utils.py
|
e43bccf088d41592440e088c2871e621edc56919 |
|
14-Aug-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] improve test_that's logging This CL accomplishes a few things: 1) Makes the output format of logging messages in test_that more in line with the rest of autotest. 2) Makes test_that drop log files (test_that.DEBUG, .ERROR, .INFO, and .WARNING) into the debug/ subdirectory of its logging directory. 3) Adds a --debug flag which allows the user to optionally see DEBUG level messages in stdout. 4) In order to make the logs more readable, test_that is now calling autoserv with its --no-console-prefix flag. BUG=chromium:273256 TEST=Unit tests pass Change-Id: I8b2c4594f22de40ddd25a2ba84214f65021f5c29 Reviewed-on: https://gerrit.chromium.org/gerrit/65893 Commit-Queue: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/autoserv_utils.py
|
c14951af46e88db7574b9e01ff77d2e419e8058e |
|
13-Aug-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] add ssh_verbosity to test_that and autoserv_utils BUG=chromium:271621 TEST=unit tests pass. Manually verified that flag works as expected. Change-Id: I31c59a80a7a2151c27d4a41ff8c6cfbf51d259cb Reviewed-on: https://gerrit.chromium.org/gerrit/65720 Commit-Queue: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/autoserv_utils.py
|
f6b5aaeef62ea9eb77f7c351db1ebf079c87dc3f |
|
09-Jul-2013 |
Christopher Wiley <wiley@chromium.org> |
autotest: Add --fast flag to test_that test_that will turn off some slow autoserv functionality that developers are unlikely to miss if this flag is passed. TEST=Ran test_that with this flag, noted that tests ran faster and appropriate logging was emited/omited. BUG=chromium:258509 Change-Id: I470c1e2392ed20d775f97459d0d52bf29ea92396 Reviewed-on: https://gerrit.chromium.org/gerrit/61304 Tested-by: Christopher Wiley <wiley@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org> Commit-Queue: Christopher Wiley <wiley@chromium.org>
/external/autotest/server/autoserv_utils.py
|
308e7367e576ea26b2723aa112c178cb0568b5a4 |
|
21-May-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] pull _autoserv_command_line functionality into utility module This CL pulls the logic used by monitor_db.py to create an autoserv command line from a job into its own function, in a separate new module -- autoserv_utils.py. This will allow for code reuse with test_that. monitor_db still contains a number of other functions which create autoserv command lines for other tasks like log collection. These have not yet been pulled out to shared utility functions, because those parts of the scheduler didn't seem to have any unit test coverage. A future CL may pull some of these out as well. BUG=chromium:236471 TEST=unit tests pass. Ran a smoke suite in local autotest. DEPLOY=scheduler Change-Id: I6317b70aa9fb7e9968739582b9379112baa4507b Reviewed-on: https://gerrit.chromium.org/gerrit/56136 Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Commit-Queue: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/autoserv_utils.py
|