| 89c442d38060c715b5457dceaa0c9430b90c04f7 |
|
15-Feb-2017 |
Achuith Bhandarkar <achuith@chromium.org> |
autotest: Move is_arc_available to lsbrelease_utils.py
BUG=None
TEST=trybots
Change-Id: Ifcfd11af33620d5850f0dbf18018d70b72c55f3f
Reviewed-on: https://chromium-review.googlesource.com/443184
Commit-Ready: Achuith Bhandarkar <achuith@chromium.org>
Tested-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| f57080024280104e5c3b236f69d1629d597fa5b6 |
|
18-Feb-2016 |
Katherine Threlkeld <kathrelkeld@chromium.org> |
[Autotest] Check Bluetooth naming format inside of bluetooth_IDCheck test.
A recent change appends some identifying numbers on the end of the
Bluetooth adapter alias. E.g. "Chromebook_1234" instead of just
"Chromebook".
The bluetooth_IDCheck test already verified the format of the ID.
This change makes it also verify the new naming convention.
Also, add a common utils function to get the device_type string
from /etc/lsb_release.
TEST=ran on several devices
BUG=chromium:585965
Change-Id: Ia347b975f918aeb5a91a2f196ed64ca6930d38f9
Reviewed-on: https://chromium-review.googlesource.com/328061
Commit-Ready: Katherine Threlkeld <kathrelkeld@chromium.org>
Tested-by: Katherine Threlkeld <kathrelkeld@chromium.org>
Reviewed-by: Tien Chang <tienchang@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| e0b08e6170b57f90262726eb7f04e059cb47419c |
|
11-Aug-2015 |
Hsinyu Chao <hychao@chromium.org> |
Revert "autotest: move constants to common_lib"
This reverts commit a4ac7a8f67d61f8a616724f9426dbc0fce71ce69.
BUG=chromium:519353
Change-Id: Iec2873ad22b5bb90e46a9e5b323f9626a2c07d9b
Reviewed-on: https://chromium-review.googlesource.com/292347
Reviewed-by: Hsinyu Chao <hychao@chromium.org>
Commit-Queue: Hsinyu Chao <hychao@chromium.org>
Tested-by: Hsinyu Chao <hychao@chromium.org>
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Queue: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| a4ac7a8f67d61f8a616724f9426dbc0fce71ce69 |
|
06-Aug-2015 |
Eric Caruso <ejcaruso@chromium.org> |
autotest: move constants to common_lib
This file gets imported from lots of server-side tests and
infrastructure so it shouldn't be hiding in client/cros. This
moves the file and fixes all imports.
BUG=chromium:485834
TEST=run many tests, make sure there are no problems importing
constants
Change-Id: I5c2b2a0bef6ebc998e62f40162a6ec9cc4436480
Reviewed-on: https://chromium-review.googlesource.com/291302
Trybot-Ready: Eric Caruso <ejcaruso@chromium.org>
Commit-Queue: Eric Caruso <ejcaruso@chromium.org>
Tested-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Chris Sosa <sosa@google.com>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| 8b8d0ea923985dd39a01c64c79a15c4ca3f31372 |
|
31-Mar-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Check existance of lsb-release file before testing chromite lib.
To check if the process is running in moblab, try to use lsb-release file
before testing if chromite lib call IsInsideChroot.
This is to avoid confusion of the error message "Unable to determine if this
is a moblab system"
BUG=None
TEST=local call lsbrelease_utils.is_moblab.
Change-Id: Ie1c325971e6947ef300770c33150987abbed5759
Reviewed-on: https://chromium-review.googlesource.com/263284
Trybot-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| 549fb82f8dd7ad8031fa451cb19bb1f56355f08c |
|
25-Mar-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Add code in verify and cleanup to remove cros-version label if it doesn't match
Make sure the dut's cros-version label matches the actual version stored in
lsb-release under attribute CHROMEOS_RELEASE_VERSION.
It's added to both cleanup and verify because:
1. If a test failed by dut issue or autoserv crash, cleanup will be queued.
the lab gets a chance to verify the cros-version label before the dut being
assigned to another test.
2. verify is called before each test, so confirming the cros-version label
there is necessary.
The check takes only one ssh call to the dut. Making a duplicated check (reset
calls both cleanup and verify) should not lead too much overhead.
BUG=chromium:469895
TEST=unittest, run local test
1. Add a cros-version label that matches lsb-release, run dummy test, confirm
the label is preserved.
2. Add a cros-version label doesn't match lsb-release, run dummy test, confirm
the label is removed by verify task, and verify job failed.
Change-Id: Ia4760967118f2aacfe5c7f378bb482df7995cef3
Reviewed-on: https://chromium-review.googlesource.com/262390
Trybot-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| 2a0a1ff986fc4fe0e817e2ce5745b4997b5eac27 |
|
05-Mar-2015 |
David Haddock <dhaddock@chromium.org> |
Update for image comparison tests
The initial checkin didn't have version control. This adds it.
A folder structure like <milestone>/<golden image> is now on Google Storage.
The Roboto font change broke everything so we need versioning.
This also adds a bigger timeout as the lab takes longer than my local testing.
This also adds a few fixes due to accessibility fixes in ChromeOS.
BUG=None
TEST=None
Change-Id: I33d994122bebe413344c8cb18d6341e3975a5747
Reviewed-on: https://chromium-review.googlesource.com/255751
Reviewed-by: Mussa Kiroga <mussa@chromium.org>
Reviewed-by: Kris Rambish <krisr@chromium.org>
Commit-Queue: David Haddock <dhaddock@chromium.org>
Tested-by: David Haddock <dhaddock@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| e8cef9501dbb580e1629d1d3ae93c3edbe2e294b |
|
07-Feb-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Check if it's running in chroot when determining if the system is moblab
BUG=chromium:454583
TEST=test_that, confirm no error message:
"Unable to determine if this is a moblab system"
Change-Id: I3ae7e0ad47bc00f2098dde4342384dbdc7aa5dbe
Reviewed-on: https://chromium-review.googlesource.com/247408
Trybot-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|
| 60cf6a9294dc53a9fe11dc9b28eaaea1ee69ca92 |
|
30-Jan-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Add a moblab_config to override config value in global config when running in moblab.
The config value set in moblab_config.ini will override values in global
config only when running in moblab. Shadow config values can override
what's set in moblab config.
The config file can be used to disable particular function of autotest that
can be used in test lab but not moblab.
Also fix a bug in server management.
BUG=chromium:377210
TEST=unittest, local autoest setup to confirm shadow config not affected.
DEPLOY=apache
Change-Id: If199ba34f0047776ca8915a445b0d4fe5716e716
Reviewed-on: https://chromium-review.googlesource.com/244170
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/lsbrelease_utils.py
|