5ace6f2e17f808efbee863a7d7dbe1bc52527a19 |
|
07-Jan-2016 |
Simran Basi <sbasi@google.com> |
[autotest] Support Android/Brillo suite runs. This change does 3 key things: 1) Enables suite runs to use the production code currently deployed on the lab servers. This disables this requirement and now run_suite.py can be passed --run_prod_code. This means that it will use the control files on the drone and SSP has been disabled. 2) Refactors out the AFE interactions for applying version labels out of the host objects. These utilities are in a new module called afe_utils. The afe_utils:host_in_lab function determines if a host is running in an lab environment and if it is in the AFE. The introduction of afe_utils enables further cleanup of the cros_host object. 3) Enables provisioning for Android/Brillo devices. Added a new site-test and provision attribute. Run_suite will determine if an Android/Brillo build is being used and will set the correct version prefix. Then the scheduler/provision code will find an appropriate device and kick off the provision_AndroidUpdate test to install the build prior to test runs. BUG=chromium:574566 TEST=On my moblab: ./run_suite.py --build=git_mnc-brillo-dev/dragonboard-userdebug/2558576 \ --board=brillo-dragonboard --suite_name=brillo-bvt --run_prod_code \ --pool='' ./site_utils/run_suite.py --board=peppy --build=peppy-release/LATEST \ --suite_name=dummy --pool='' test_that 100.96.51.40 dummy_PassServer DEPLOY=apache Change-Id: I5a81e6bd989188b7c0621e2a76752a39033f9782 Reviewed-on: https://chromium-review.googlesource.com/323781 Commit-Ready: Simran Basi <sbasi@chromium.org> Tested-by: Simran Basi <sbasi@chromium.org> Reviewed-by: Christopher Wiley <wiley@chromium.org> Reviewed-by: Fang Deng <fdeng@chromium.org> Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
a6adc7a1ec6c1ebb5db420da12ab9f6e5314db05 |
|
30-Aug-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] add pattern matching ability to test_that's tests arg This CL adds two type of test pattern matching to test_that. Patterns can now be specified with e:[test name pattern] or f:[file name pattern] as the TEST argument to test_that. It also demotes the complaint "Getting control files for a specific suite has not been implemented for FileSystemGetter.' to DEBUG level, so it doesn't cause test_that user confusion. BUG=chromium:214066 TEST=Unit tests pass. Also... Suite names still work the same way: $ test_that [remote] suite:smoke # smoke suite scheduled correctly Test name patterns work, like this: $ test_that [remote] e:cantelope # No tests scheduled, test_that errors out $ test_that [remote] e:dummy # No tests scheduled $ test_that [remote] e:dummy.* # 6 tests whose name begin with dummy # scheduled File name pattern work, like this: $ test_that [remote] f:dummy # # No tests scheduled. $ test_that [remote] f:.*dummy.* # 8 tests scheduled $ test_that [remote] f:.*server.*dummy.* # 2 tests scheduled $ test_that [remote] f:.*client.*dummy.* # 6 tests scheduled Change-Id: I104847bdf7956e020f2581128946471d1794b8d2 Reviewed-on: https://chromium-review.googlesource.com/167668 Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Commit-Queue: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
c594c1c3ed039635462371af90562475fcee575e |
|
10-Jul-2013 |
beeps <beeps@chromium.org> |
[autotest] Pipe suite_name through client devserver code. To reduce the overhead involved with fetching control files from the devserver we generate a mapping of suite->control files at build time. This cl will ask the control file getter to fetch the control files for a given suite instead of all the control files associated with an image. Also removing SUITE = None from some networking test control files, and patched unittests. BUG=chromium:252398 TEST=Ran a suite with many control files. Made sure the suite-> control file mapping falls back to the old code when a bad suite name is specified. Compared the test objects created in the old version vs those created with this change. Ran unittests. CQ-DEPEND=CL:I6b590c8c40a863e6744875a26ac228ffd4dd8794 Change-Id: I4274c78764ffaaabef1ed48cdb40f523e307938d Reviewed-on: https://gerrit.chromium.org/gerrit/63182 Tested-by: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
35476b958f33c6bada2932237a97f59b483b451d |
|
24-Jul-2013 |
Prashanth Balasubramanian <beeps@chromium.org> |
Revert "[autotest] Pipe suite_name through client devserver code." This reverts commit 5a80a9be9f8ff74675c8696b9c18dc6b19bb625c Change-Id: Ic483b7a27b2603f533819cea3df33522596c5848 Reviewed-on: https://gerrit.chromium.org/gerrit/63171 Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
5a80a9be9f8ff74675c8696b9c18dc6b19bb625c |
|
10-Jul-2013 |
beeps <beeps@chromium.org> |
[autotest] Pipe suite_name through client devserver code. To reduce the overhead involved with fetching control files from the devserver we generate a mapping of suite->control files at build time. This cl will ask the control file getter to fetch the control files for a given suite instead of all the control files associated with an image. Also removing SUITE = None from some networking test control files, and patched unittests. BUG=chromium:252398 TEST=Ran a suite with many control files. Made sure the suite-> control file mapping falls back to the old code when a bad suite name is specified. Compared the test objects created in the old version vs those created with this change. Ran unittests. CQ-DEPEND=CL:I6b590c8c40a863e6744875a26ac228ffd4dd8794 Change-Id: Ic1d65672e8c65b728b9d783f60f3093c7d0d866b Reviewed-on: https://gerrit.chromium.org/gerrit/61402 Commit-Queue: Prashanth Balasubramanian <beeps@chromium.org> Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org> Tested-by: Prashanth Balasubramanian <beeps@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
58e8a4c9c6e6abd8c2a21ad55238c613d0232cb1 |
|
04-Jun-2013 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] delint control_file_getter.py Removed unused imports. As a side effect of this, no longer importing compiler module, so no longer emitting deprecation warning. BUG=chromium:235607 TEST=unit tests; Ran smoke suite in local autotest instance. Change-Id: Ie5237793b274c06da1c60817a27d10b91aecfc1d Reviewed-on: https://gerrit.chromium.org/gerrit/57484 Commit-Queue: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
accb5ceaac066025592808247bfa9c97966bba97 |
|
31-Aug-2012 |
Chris Sosa <sosa@chromium.org> |
Support graceful failover/aggregation for autotest devserver pool. This change implements the graceful failover/aggregation designed in crosbug.com/26451. This required a large re-work of how other modules interact with the dev_server module. Instead of always relying on being able to pass in the "build" to any dev_server RPC, a caller must start by using the static resolve method that resolves a build to an ip addr and creating a DevServer instance from that hostname. i.e. ds = Devserver.create() ds.trigger_download('build') turns into ds = ImageServer.resolve('build') ds.trigger_download() In order to guarantee the re-use of the same hostname throughout the life-cycle of a suite run, we keep the hostname as part of the suitespec and also parse the package_url based on the image_url -- not the build. As noted, I've also separated the imaging / crash components into their own DevServer subclasses to simplify the interaction and modified callers. BUG=chromium-os:26451 TEST=Unittests so far + local autotest setup with running bvt suite on one host in the lab + ran suite_enumerator with/without -l Change-Id: I4760e4033bb347259e3bb30f2fac31f321654c6f Reviewed-on: https://gerrit.chromium.org/gerrit/32006 Commit-Ready: Chris Sosa <sosa@chromium.org> Reviewed-by: Chris Sosa <sosa@chromium.org> Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
52550b962368aec79cdde077485af91629550582 |
|
05-Sep-2012 |
Alex Miller <milleral@chromium.org> |
[autotest] Filter out debian control files. When caching the list of control files from the file system or devserver, strip out any control files that end in 'src/debian/control'. This way, we can't mistake files that are a part of the debian packaging system as files that are a part of the autotest system. BUG=chromium-os:33916 TEST=ran local dummy suite, verified warnings about src/debian/control files no longer occurred. Change-Id: I9273bc94c753bca8f43d7f27335a723b10c6e128 Reviewed-on: https://gerrit.chromium.org/gerrit/32260 Tested-by: Alex Miller <milleral@chromium.org> Reviewed-by: Scott Zawalski <scottz@chromium.org> Commit-Ready: Alex Miller <milleral@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
db06e077db87fe373d152f34895148784301744d |
|
05-Sep-2012 |
Alex Miller <milleral@chromium.org> |
Revert "[autotest] Skip debian control files." This reverts commit ac1ffe5a18ffc05e2661877db0cd611a3ca06b85 as I9273bc94c753bca8f43d7f27335a723b10c6e128 will achieve the same thing, but in a cleaner and more comprehensive fashion. BUG=chromium-os:33916 TEST=None Change-Id: I9b1675d988faca01c5e52677eac6eb3d422ffe7d Reviewed-on: https://gerrit.chromium.org/gerrit/32267 Tested-by: Alex Miller <milleral@chromium.org> Reviewed-by: Scott Zawalski <scottz@chromium.org> Commit-Ready: Alex Miller <milleral@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
ac1ffe5a18ffc05e2661877db0cd611a3ca06b85 |
|
28-Aug-2012 |
Alex Miller <milleral@chromium.org> |
[autotest] Skip debian control files. Currently, when we're looking through the source tree for control files and accidentally grabing files that are a part of the debian packaging system. This change discards any files we find that are in a |src/debian| directory. BUG=chromium-os:33916 TEST=ran dummy suite locally and no warnings happened Change-Id: Iaf144931225138f17bca7409977bf1182e67693c Reviewed-on: https://gerrit.chromium.org/gerrit/31537 Commit-Ready: Alex Miller <milleral@chromium.org> Reviewed-by: Alex Miller <milleral@chromium.org> Tested-by: Alex Miller <milleral@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|
b493555db2d43e79d96e793cae9d1ffb822dd6c1 |
|
14-Aug-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Move dynamic suite code into its own module No big rewrite, just moving files around BUG=chromium-os:30266 TEST=unit TEST=successful run_suite.py run TEST=suite_enumerator.py, suite_preprocessor.py, and suite_scheduler.py Change-Id: I2fbcae0332104ce3adcb10a1e90ce94cb209aca8 Reviewed-on: https://gerrit.chromium.org/gerrit/30267 Reviewed-by: Scott Zawalski <scottz@chromium.org> Commit-Ready: Chris Masone <cmasone@chromium.org> Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/server/cros/dynamic_suite/control_file_getter.py
|