| b5420a7d676be0c152ca6aa91cafbadb145d5bcd |
|
20-Jun-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Extract _get_metric_fields()
BUG=chromium:732588
TEST=None
Change-Id: Ifd78cc0c44bccf2f2a0d811005821030f8b335bf
Reviewed-on: https://chromium-review.googlesource.com/549088
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 1a5cc0a2acf66ed9a93fd270ca1e34c005107fde |
|
20-Jun-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Get rid of to_raise exception storing
BUG=chromium:732588
TEST=None
Change-Id: Ie0dbaa1692e1d3fd4d57978e4ad8d24da3d70045
Reviewed-on: https://chromium-review.googlesource.com/549087
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 3e96cc24b38bd15c19cee0ba79de2b4c3297a910 |
|
08-Jun-2017 |
Gwendal Grignou <gwendal@chromium.org> |
autoupdate: Install stateful_update from the right location
stateful_update can be locally stored at 2 locations:
/usr/sbin/stateful_update installed by package chromeos-base/devserver,
or by python modules: either during unit test or by build_externals.py on
the labserver.
BUG=chromium:689105
TEST=Unit test. Test stateful_update is executable.
Check powerwash machines are updating properly.
Change-Id: Ib43552651b7b1bae594254253b0d623f5e72f8a5
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/527422
Reviewed-by: Richard Barnette <jrbarnette@google.com>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| ff1d8babb1961ff7324de380f8f592005431c9e4 |
|
16-Jun-2017 |
David Haddock <dhaddock@chromium.org> |
[autotest] Remove Brillo v1 update code.
The BrilloUpdater/BrilloTestPlatform implementation was for version one
of Brillo. This is no longer in use. Confirmed by Brillo Test Engineer.
As part of autoupdate_EndToEndTest rewrite, I will remove this code.
BUG=chromium:709710
TEST=test_that chromeos2-row3-rack10-host13.cros autoupdate_EndToEndTest
Change-Id: I7a5500ea14c33fde7d4cc998d1f536130868e371
Reviewed-on: https://chromium-review.googlesource.com/538915
Commit-Ready: David Haddock <dhaddock@chromium.org>
Tested-by: David Haddock <dhaddock@chromium.org>
Reviewed-by: Justin Giorgi <jgiorgi@google.com>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| f15c8fc1d0842903074da84e462822d04dda2ce1 |
|
03-Mar-2017 |
Luigi Semenzato <semenzato@chromium.org> |
autoupdate test: retry if update_engine daemon has not started yet
We see that update_engine_client fails to connect to update_engine
shortly after boot because update_engine has not started yet.
In such case, we wait a bit and retry.
Some restructuring is needed to share the functionality between
trigger_update() and run_update()
BUG=chromium:690232
TEST=ran on test shard
Change-Id: I596f2fd88462af3d56a5d33ead33fad525fabb6e
Reviewed-on: https://chromium-review.googlesource.com/449975
Commit-Ready: Luigi Semenzato <semenzato@chromium.org>
Tested-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 5e2efb71ffebead22aa4f0744ad843ee79814b43 |
|
07-Feb-2017 |
Dan Shi <dshi@google.com> |
[autotest] Use the metrics_mock object in case chromite is not set up.
BUG=chromium:688166
TEST=unittest
Change-Id: Ic0077cb2dba75a8d820f229060f3f70f507850a1
Reviewed-on: https://chromium-review.googlesource.com/438754
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| a5cfb97ee793d849acf0efa4369b43d6f91a9c4d |
|
28-Dec-2016 |
Allen Li <ayatane@chromium.org> |
[autotest] Add get_hostname_addr_map() (squashed)
BUG=chromium:666022
TEST=None
!Change-Id: I9b3385fd8fba91f67fe968bb7bf85d39792e8c16
[autotest] Add hostname property to devserver
BUG=None
TEST=None
!Change-Id: I7fcd9b92d3c086ea9a8e6a4749f65b65a827855f
[autotest] Extract get_hostname() function
BUG=None
TEST=None
!Change-Id: I45f7a8e4f3f57beb77df6766fbe5747ebe295613
[autotest] Replace get_server_name with get_hostname
BUG=None
TEST=None
!Change-Id: I75ebfe05ccd1f4d9209d68bc0e5f2db691558a74
[autotest] Add _reverse_lookup_from_config()
BUG=chromium:666022
TEST=None
!Change-Id: I1ea54296cc5a7a67981338c1c3d4057b065fa279
[autotest] Attempt to look up devserver hostname for metrics
BUG=chromium:666022
TEST=None
!Change-Id: I3dec24d4874de66466a373c97de5364c4b1ba557
[autotest] Make get_section_as_dict() ordered
The ordering information is preserved in the config file, so may as
well preserve it here.
BUG=chromium:666022
TEST=None
!Change-Id: I46b9fa47fa87b789a4e63563797a4327ac308bef
[autotest] Clarify _reverse_lookup behavior for duplicates
BUG=chromium:666022
TEST=None
!Change-Id: I839ba7b55005b6137fa03887854ea59dfee49dfa
Change-Id: I0aeb05d16d8fc8b98987dc232da8928ddd9fdb9f
Reviewed-on: https://chromium-review.googlesource.com/424913
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| e76d9f8b9cfa7d1075d3d757f82b9a8792690886 |
|
21-Nov-2016 |
Luigi Semenzato <semenzato@chromium.org> |
autoupdate tests: retry update_client on network errors
We see many autoupdate test failures from network errors
(update_client error 37 and broken ssh connections) which
may succeed on retry. This change makes the test retry
once for those errors.
BUG=chromium:657548
TEST=none
Change-Id: Id74272639ace343e6f1932a8f4d60db4eec50fb2
Reviewed-on: https://chromium-review.googlesource.com/413076
Commit-Ready: Luigi Semenzato <semenzato@chromium.org>
Tested-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 14cac44542bc6a403cb7a3585eb3ebae00227992 |
|
21-Nov-2016 |
Aviv Keshet <akeshet@chromium.org> |
autotest: move or eliminate a bunch of autotest_stats stats
BUG=chromium:667171
TEST=unittests; guado_moblab tryjob + test run
Change-Id: I815d2d748a2daa3bc869ead5d09f722245b7317b
Reviewed-on: https://chromium-review.googlesource.com/413103
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 61d289840e3482df2ef0cf74832a6d707def2ac2 |
|
28-Oct-2016 |
Shelley Chen <shchen@chromium.org> |
[autotest] adding in board,build_type,milestone in autoupdater
BUG=chromium:655782
BRANCH=None
TEST=None
Change-Id: I40828ff3a43befd7863a09f8171fb282080e68ea
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/404868
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 16b8df37317c901e03bba2ced92ff0f91cfa3315 |
|
28-Oct-2016 |
Shelley Chen <shchen@chromium.org> |
[autotest] Add metric collection during autoupdate
Adding in collection of metrics when autoupdate
command completes. Currently only for devserver
and success/failure.
BUG=chromium:655782
BRANCH=None
TEST=None
Change-Id: If1270a7d5c9eec2ee05d81bce900a9c47c23ab40
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/404554
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| fe4d62e304695d4e2a35993af15740b74a416ee8 |
|
23-Jun-2016 |
Shuqian Zhao <shuqianz@chromium.org> |
update_engine: Add retry to the update_engine check status call
Based on the discussion in the bug, there could exist a race condition
between the update_engine start deamon and the update_engine_client
call. Add a retry to check_update_status call to wait for the update_engine
is ready. And also remove the 2>&1 in several places to show up the logs that
could helpful for debug.
BUG=chromium:588828
TEST=TEST in a test DUT. Stop update_engine on the DUT, and run the check
status call and the DUT retried.
Change-Id: I214f5029397c25847c4ed52590b00a10bc918227
Reviewed-on: https://chromium-review.googlesource.com/355692
Commit-Ready: Shuqian Zhao <shuqianz@chromium.org>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
Reviewed-by: Shuqian Zhao <shuqianz@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| ccf2e72170237a6111d56c6956eb1732972a9ad8 |
|
11-Jun-2016 |
xixuan <xixuan@google.com> |
Autotest: delete http call to devserver for new ACL
Since new ACL forbiddens all ports except for port 22, this CL deletes the
direct http call to devserver in pre-check process of auto-update. It's
replaced by devserver healthy check, which uses inherited call to connect
to devserver. The inherited call in devserver use port 22 when the new ACL
applies.
BUG=chromium:618510
TEST=run local autotest instance and 'repair' job for dut to check the logic.
Change-Id: Ib30af06d34df68c0fca608b3263397ca49796b9f
Reviewed-on: https://chromium-review.googlesource.com/351681
Commit-Ready: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 18ed0ea21e71afb9a5da1b7511c1efbbae8523d6 |
|
09-Jun-2016 |
xixuan <xixuan@google.com> |
Autotest: add logging to record the IOError in connection to devserver.
BUG=chromium:618510
TEST=None
Change-Id: I76e2dbc49a36a727df62af93f4e39790604a09c0
Reviewed-on: https://chromium-review.googlesource.com/351091
Reviewed-by: Kris Rambish <krisr@chromium.org>
Commit-Queue: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| f37b2d72fd2fd7a21a8cc0a377b2f93d53f75a68 |
|
02-Jun-2016 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] eliminate exception-passing multiprocess queue
Now that multiprocess usage has been eliminated, we no longer need the
complexity of the update_error_queue
BUG=chromium:547548
TEST=trybot
Change-Id: I13bc02306ebac68eb0d0a6795b39af8a4cbe0830
Reviewed-on: https://chromium-review.googlesource.com/348961
Commit-Ready: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 2610d3e4da4a3af1884b56dc8299974beb2a7ed0 |
|
02-Jun-2016 |
Aviv Keshet <akeshet@chromium.org> |
[autotest] autoupdater.py run rootfs update and stateful update in series
Stateful update takes <1 minute, and running it in parallel with rootfs
update only adds complexity to the logs and risk of flake.
BUG=chromium:547548
TEST=moblab tryjob
Change-Id: I8f60a7398973accd00d47b0e924366bbbbca0209
Reviewed-on: https://chromium-review.googlesource.com/348857
Commit-Ready: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| c2a15ebfadd2a3cf4ab369b3d0c4a868ce99505c |
|
31-Mar-2016 |
Shuqian Zhao <shuqianz@chromium.org> |
[autotest] print out the original exception when running update
The original exception of running update is helpful for debug. Log it
out.
BUG=None
TEST=Unittest
Change-Id: I909f882bc091cbffcbc45c301d8056d2753d02aa
Reviewed-on: https://chromium-review.googlesource.com/336720
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
Commit-Queue: Shuqian Zhao <shuqianz@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| d999272ea09ef0541116cf39307cc6a87e8a168d |
|
29-Feb-2016 |
Shuqian Zhao <shuqianz@chromium.org> |
[autotest] show the update_engine error msg on chromeos waterfall
Every time when autoupdate test failed, we will ask the update_engine to
return the last update error messages, and show on the waterfall.
BUG=None
TEST=Unittest, trybot, and run provisioning jobs on local dut.
Change-Id: I5cb80fb45ca6eb10ef71e9b253cf00ef37c410c8
Reviewed-on: https://chromium-review.googlesource.com/329742
Commit-Ready: Shuqian Zhao <shuqianz@chromium.org>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
Reviewed-by: Shuqian Zhao <shuqianz@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| f3a35f73b2d47db2ab488f4954bc06667fc439e3 |
|
25-Jan-2016 |
Dan Shi <dshi@google.com> |
[autotest] Log time used to run autoupdater for CrOS
The stats data will be used to monitor the overall history of time used to run
AU and Paygen test.
BUG=chromium:561036
TEST=None
Change-Id: Iab43619d629885b14792962b0182ba27b182a850
Reviewed-on: https://chromium-review.googlesource.com/323397
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Alex Deymo <deymo@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 205b873e3fd99d6ed20e2d47b8317f27344a4f3e |
|
25-Jan-2016 |
Dan Shi <dshi@google.com> |
[autotest] Increase stateful_update timeout
This is to accommodate the occasionally network issue in the lab. The lab
devservers sometime are overloaded and the slow network can cause paygen runs
to timeout.
BUG=chromium:561036
TEST=None
Change-Id: I5d60319bc405caab2420bfc3d6ad22a79c8e0271
Reviewed-on: https://chromium-review.googlesource.com/323409
Trybot-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Kevin Cheng <kevcheng@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| d035b0c458560c0421620a63191328522ff880a7 |
|
21-Jan-2016 |
Alex Deymo <deymo@chromium.org> |
Increase payload application timeout to 1h.
The update_engine_client command ran from update_image() had a timeout
of 20 minutes. This command blocks until the payload is downloaded and
applied in the DUT. Due to network load or server side load, the
payload application started to take more than 20 minutes, with a
steady but slow download speed.
This CL bumps the limit to 1h and lets the whole test suite timeout
instead of failing to apply the payload.
BUG=chromium:580261
TEST=None
Change-Id: I07bad14ae1a6fd28d22ed371d920953268b8ef05
Reviewed-on: https://chromium-review.googlesource.com/322866
Trybot-Ready: Alex Deymo <deymo@chromium.org>
Tested-by: Alex Deymo <deymo@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 3e765032e34dacf797befb1ee31fcb159d7a72bf |
|
09-Oct-2015 |
Gilad Arnold <garnold@chromium.org> |
autoupdater: Provide more detail on failure.
BUG=None
TEST=None
Change-Id: I4bb97fd1b6efc810f9347414742377e6f39ed52d
Reviewed-on: https://chromium-review.googlesource.com/304906
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| ecf894b60e77db4f827b0a7ea03f366adf8950bd |
|
07-Oct-2015 |
Gilad Arnold <garnold@chromium.org> |
autoupdater.py: Fix bogus use of super() in BrilloUpdater.
BUG=b:24157043
TEST=autoupdate_EndToEnd on moblab doesn't fail with TypeError
Change-Id: Ie8ac782e8ab6a60881a0847c6904a1a5aa519085
Reviewed-on: https://chromium-review.googlesource.com/304570
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| d6adeb8e407b50a5332976342a1ad2d457a081e5 |
|
21-Sep-2015 |
Gilad Arnold <garnold@chromium.org> |
autoupdater.py: Implement BrilloUpdater.
This extracts shared updater functionality from ChromiumOSUpdater into
a new class (BaseUpdater) and implements BrilloUpdater based on it.
Currently extracted logic is meant to support the autoupdate_EndToEnd
server-side test; we may pull more as we expand support for other tests.
BUG=b:24157043
TEST=AU E2E test ran successfully on moblab w/ peppy DUT (sbasi@)
TEST=Unit tests
Change-Id: I73243560dcf6938f56d1c87364d5f5800dc0cd12
Reviewed-on: https://chromium-review.googlesource.com/301402
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Gilad Arnold <garnold@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 62cf3a47fb75b5abf367dcc684234e9bd89459f1 |
|
01-Oct-2015 |
Gilad Arnold <garnold@chromium.org> |
autoupdater.py: Improve error reporting of certain operations.
Clarify and add detail to the errors reported by three methods that are
used by the autoupdate_EndToEnd test.
BUG=b:24530765
TEST=Unit tests
Change-Id: I2392f27fd6724e5b3249cc04d4d351c8d2b6ed3a
Reviewed-on: https://chromium-review.googlesource.com/303156
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 0c0df7324b80a8fcf41739705b3bcbd10d3e2b8b |
|
21-Sep-2015 |
Gilad Arnold <garnold@chromium.org> |
autoupdater.py: move CrOS-specific constants into ChromiumOSUpdater.
We'll soon have a new implementation (with different assumptions) for
Brillo devices.
BUG=b:24157043
TEST=Linter + unittests
Change-Id: I87c0dcae0cb8d646329b1a27aaf4403d6bf14aec
Reviewed-on: https://chromium-review.googlesource.com/301401
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 5f2ff44e311ce949e24a7e8c4f1b12c65fee81f1 |
|
21-Sep-2015 |
Gilad Arnold <garnold@chromium.org> |
autoupdater: Fix whitespace errors.
BUG=None
TEST=None
Change-Id: If8c4cdf7952df882f63422fc3ceeb5861a9a8cc3
Reviewed-on: https://chromium-review.googlesource.com/301400
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| e92399e32d4e83d7eb01b5c56e53c301a2a6dbc7 |
|
24-Apr-2015 |
Chris Sosa <sosa@chromium.org> |
Re-land: Autotest: rewrite machine_install to be robust to devserver flakiness.
This CL both simplifies machine_install as well as adds protections
when devservers are flaky to provisioning.
1) I simplified machine_install's repair logic by having it in one place
rather than scattered throughout machine_install and using the same
pre-condition state for all machine_install's (rather than a heavier one just
for repair).
2) Added a loop around the actual full update. Basically, I've added a #
of attempts for update. If an update fails, I will run a health check against
its devserver and re-attempt on another devserver if it's failed. This includes
re-staging the image on the other devserver as well as updating from it.
BUG=chromium:470581,chromium:471294
TEST=Moblab + Dynamic Suite + Instrumented Code to fail Autoupdate once to
check fallback + unittests in autoupdater.py + pyflakes/pylint on all
affected files.
Change-Id: I5b73a41db32ec832202f6f09f51604b62640b2b6
Reviewed-on: https://chromium-review.googlesource.com/267121
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 0b023a7b8033a731c88c102477c450667071f224 |
|
24-Apr-2015 |
Richard Barnette <jrbarnette@chromium.org> |
Revert "Autotest: rewrite machine_install to be robust to devserver flakiness."
This reverts commit fe703e7073de95239d882e102d9a8d36caf9ac30.
This is suspected of breaking Repair jobs
BUG=chromium:481014
TEST=None
Change-Id: I91dab872587f9a23f784303d34d7dcf056dbe2c4
Reviewed-on: https://chromium-review.googlesource.com/267078
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| fe703e7073de95239d882e102d9a8d36caf9ac30 |
|
08-Apr-2015 |
Chris Sosa <sosa@chromium.org> |
Autotest: rewrite machine_install to be robust to devserver flakiness.
This CL both simplifies machine_install as well as adds protections
when devservers are flaky to provisioning.
1) I simplified machine_install by entirely removing the repair option
which was only referenced internally to this module as well as by one
autoupdate job that is not used anymore. I have remove that job in a previous
CL. Repair basically didn't need to exist. There was redundancy for it and
it's cleaner to just have a clean slate before ANY update.
2) Added a loop around the actual full update. Basically, I've added a #
of attempts for update. If an update fails, I will run a health check against
its devserver and re-attempt on another devserver if it's failed. This includes
re-staging the image on the other devserver as well as updating from it.
BUG=chromium:470581,chromium:471294
TEST=Moblab + Dynamic Suite + Instrumented Code to fail Autoupdate once to
check fallback + unittests in autoupdater.py + pyflakes/pylint on all
affected files.
Change-Id: I9836399269427e00fb6ccbcc79a08e0b11ef8859
Reviewed-on: https://chromium-review.googlesource.com/265954
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 0942b1df911f6d78b0bc4277456de01ebbf9e5ec |
|
31-Mar-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Add get_release_version method to servo_host
get_build_id method in autoupdater was removed. Add the new method for
servo_host to use.
BUG=chromium:472135
TEST=local servo test, confirm verify servo works
Change-Id: Ic255dce3b7bfa361204bd6dd7bb03b8f86ec6c5e
Reviewed-on: https://chromium-review.googlesource.com/263245
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>
/external/autotest/client/common_lib/cros/autoupdater.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/cros/autoupdater.py
|
| 3b858a2c432caad62403fa646508688e2d419a13 |
|
18-Mar-2015 |
Simran Basi <sbasi@google.com> |
Catch all errors when provisioning & make start_master_ssh multiprocess safe
Currently autoupdating.py only catches AutoservRunErrors when
updating the rootfs and stateful, thus allowing autotest
infrastructure errors to not be caught properly.
Updates start_master_ssh so that it protects against multiple
processes cleaning up the old connection and creating a new one
in parallel.
BUG=chromium:468062
TEST=provision still works on moblab.
Change-Id: I5a2c31ead5b15ca66c1f8035df27e9c3420b41a8
Reviewed-on: https://chromium-review.googlesource.com/260664
Trybot-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Commit-Queue: Simran Basi <sbasi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| c861752763c8cb0d780a2933996e53af419d6fa3 |
|
10-Jun-2014 |
Chris Sosa <sosa@chromium.org> |
Re-land "Rollback: check for can_rollback before performing rollback."
This CL is a re-land of 4acbaa6864842f3464cf8816b01faf92424ead06.
In addition to re-landing it adds a build number check and unittests
that verify this functionality.
BUG=chromium:366508
TEST=Unittests
Change-Id: I6fbed8ca9d627526e35a189e2cdae037ae2d3ed1
Reviewed-on: https://chromium-review.googlesource.com/203162
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Alex Vakulenko <avakulenko@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 04be2bd5e4666a5c253e9c30ab20555e04286032 |
|
08-May-2014 |
Ilja H. Friedel <ihf@chromium.org> |
Autotest: Change logging.warn() to logging.warning().
logging.warn() is deprecated. See
http://bugs.python.org/issue13235
Substitution was performed via
~/cros/src/third_party/autotest/files$ find ./ -type f | xargs sed -i 's/logging.warn(/logging.warning(/'
BUG=None.
TEST=There should be one-- and preferably only one --obvious way to do it.
Change-Id: Ie5665743121a49f7fbd5d1f47896a7c65e87e489
Reviewed-on: https://chromium-review.googlesource.com/198793
Commit-Queue: Ilja Friedel <ihf@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 4acbaa6864842f3464cf8816b01faf92424ead06 |
|
24-Apr-2014 |
Chris Sosa <sosa@chromium.org> |
Revert "Rollback: check for can_rollback before performing rollback."
This reverts commit 4c50c54c3cd1b4c9360b27b31aa276b215dcaab9.
Due to: https://code.google.com/p/chromium/issues/detail?id=366508
can_rollback was added in R36. I need to gate this (can_rollback) with a version check.
BUG=chromium:366508
TEST=revert
Change-Id: Id2f6201fd01652895ccfbc6eded3a2356c582fdc
Reviewed-on: https://chromium-review.googlesource.com/196805
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 4c50c54c3cd1b4c9360b27b31aa276b215dcaab9 |
|
18-Apr-2014 |
Chris Sosa <sosa@chromium.org> |
Rollback: check for can_rollback before performing rollback.
This CL also removes the list_dir_contents calls as rollback
doesn't actually stage anything itself nor require something
on the devserver (it's call client-side).
BUG=chromium:356898
TEST=Tryjob + rollback test.
Change-Id: I1ac19dd40fecbc31b9d3c5ff001332b116856f68
Reviewed-on: https://chromium-review.googlesource.com/195449
Reviewed-by: Alex Vakulenko <avakulenko@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 32baa9b16e50144dfb5b59f3be46581b88890e66 |
|
13-Mar-2014 |
Prashanth B <beeps@google.com> |
[autotest] Thread list_image_dir calls through the updater.
Adds a few utility methods to the autoupdater module to list contents
of a devservers directory
TEST=Invoked the new calls to list image dir contents.
BUG=chromium:348097, chromium:349044, chromium:349047
CQ-DEPEND=CL:189674, CL:189672
Change-Id: I23100771c3bc6d70ddb2a9abeeaeb01d6d241ee7
Reviewed-on: https://chromium-review.googlesource.com/189883
Reviewed-by: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 8193956f199813f8dd0662acddc4aca8dfc20698 |
|
14-Feb-2014 |
Gwendal Grignou <gwendal@chromium.org> |
Autotest: Fix failure retrieving logs with rsync
BUG=chromium:343991
TEST=emerged
Change-Id: Icbd642a657e68e133fae20cb994330282382a6aa
Reviewed-on: https://chromium-review.googlesource.com/186660
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
Commit-Queue: Gwendal Grignou <gwendal@chromium.org>
Tested-by: Gwendal Grignou <gwendal@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 5e8c45adeeaaa493462262a1138e53d42caae014 |
|
18-Dec-2013 |
beeps <beeps@chromium.org> |
[autotest] Give servo hosts the ability to update.
Since we're now staging the latest beaglebone build on the devservers
we can update all servo_hosts that are running chromeos via update engine.
This cl forces the beaglebone to check for new updates on each reset/verify,
and if one is available, download and apply it.
TEST=Update a beaglebone with and without servo(v2).
Confirmed servod came up after the update.
BUG=chromium:272354
CQ-DEPEND=CL:178534
Change-Id: I09d0b85b81f0f60318c02e44f42b2daabe1cead4
Reviewed-on: https://chromium-review.googlesource.com/180562
Tested-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| df8aef7430bc92d8ee63c9e460be9605dc7fad6b |
|
16-Dec-2013 |
Don Garrett <dgarrett@google.com> |
Improve the standard error message in the lab if an update fails.
Produce a more meaningful (but still generic) error message in the lab
if an update fails to apply.
Take 2!
BUG=chromium:246779
TEST=New unittest + trybots
Change-Id: I9f481e9c4143d66de1d7a91f1436e9d1155aa8ab
Reviewed-on: https://chromium-review.googlesource.com/180255
Tested-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Don Garrett <dgarrett@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 83e6b54fa090935000130fd1786422d34717d055 |
|
13-Dec-2013 |
Richard Barnette <jrbarnette@chromium.org> |
Revert "Improve the standard error message in the lab if an update fails."
This reverts commit 71fe97fe10f6979e7db628e28ef0de087b79c021.
BUG=chromium:328522
Change-Id: Iec595fa3094a8079056786db88c8639209896fec
Reviewed-on: https://chromium-review.googlesource.com/180046
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 71fe97fe10f6979e7db628e28ef0de087b79c021 |
|
11-Dec-2013 |
Don Garrett <dgarrett@google.com> |
Improve the standard error message in the lab if an update fails.
Produce a more meaningful (but still generic) error message in the lab
if an update fails to apply.
BUG=chromium:246779
TEST=New unittest + trybots
Change-Id: Ib3be5fe27d7fd60732f9d20db4a08d1994358939
Reviewed-on: https://chromium-review.googlesource.com/179543
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 56b1cc83e6475b8aee1e104f28316cce6d0dfa0f |
|
07-Dec-2013 |
Don Garrett <dgarrett@google.com> |
Report kernel crashes in debug info if we rollback after update attempt.
We dump assorted debug info if an update fails and we perform a rollback.
This includes information about kernel crashes stored on stateful, if
present.
These crashes will NOT be present if the kernel crashed early in the boot
and didn't have the file system mounted.
BUG=chromium:326305
TEST=pyflakes, ran unittests.
Change-Id: I52185ef88399840e8a907d1c05d39c56ee9c959d
Reviewed-on: https://chromium-review.googlesource.com/179254
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Commit-Queue: Don Garrett <dgarrett@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| c193217c55a11367708be5c25bd1c8e1857ab6ff |
|
16-Oct-2013 |
Chris Sosa <sosa@chromium.org> |
Add rollback integration test autoupdate_Rollback.
This CL adds a rollback test that updates the DUT to a new image
and verifies that we can rollback to whatever we had installed
by inspecting the kernel state at each phase.
BUG=chromium:260568
TEST=Ran it several times.
Change-Id: Ie7f3c8ee7f0cfb4889989735f17870da19368da3
Reviewed-on: https://chromium-review.googlesource.com/173320
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 6542508ae5099864ebb88ccae0bf6cceb4e142ae |
|
16-Oct-2013 |
Chris Sosa <sosa@chromium.org> |
Refactor verification of booted partition logic so it's reusable.
The verification logic doesn't really belong to cros_host.py and putting
it there makes it difficult to re-use across server-side tests. In
a follow-up CL I plan to use verify_kernel_boot alone (to verify we
switched partitions in an update the test controls). This CL makes it
easy to do that.
BUG=chromium:260468
TEST=Ran with new test, pylint, pyflakes.
Change-Id: If81a65b3cb388e8ac5a55dbb83ba2e1617d326a2
Reviewed-on: https://chromium-review.googlesource.com/173219
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: David James <davidjames@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 0338ff3b754d52b41ca2d0432164a757daa1112d |
|
02-Oct-2013 |
Gilad Arnold <garnold@chromium.org> |
autoupdate_EndToend: improved output; robust event verification logic
This change aims at improving the quality of output during the AU
end-to-end test. In doing so, we're also robustifying the logic for
creating expected events and verifying actual events during an update
process. More specifically:
* We now use symbolic constants for specifying event type and event
result values. This means that such values are defined in one place
and there's much less room for error due to typos etc.
* Event type/result is stored in its raw form, rather than a readable
string form. The mechanism for converting a raw value to
a human-readable form is dong internally by the event class itself.
* Event verification success/failure now prints both raw and beautified
forms of both the expected and actual results. This makes it easy to
map event related info to information logged elsewhere (e.g. when new
events are consumed).
* Rootdev change message more informative (good vs bad outcome).
* We now log the fact that a test has completed all steps; this helps
a reader figure out when the test has completed successfully, and
where that point is in the logs (without this it's quite hard to
distinguish this from the rest of autotest's boilerplate logging).
* Capitalized and improved logging and exception strings.
* Rounded time differences to bounded decimal fractions (one tenth of
a second is enough).
BUG=None
TEST=Test runs successfully; logs as described.
Change-Id: Ie66677765a11778071aeaf0ad8593c5b65217d06
Reviewed-on: https://chromium-review.googlesource.com/171651
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Commit-Queue: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 66d74078caa789f80d4a43c82b61d6016a0cf430 |
|
19-Sep-2013 |
Chris Sosa <sosa@chromium.org> |
Clean up short timeouts that are causing flakes during testing.
BUG=chromium:269824
TEST=Visual + pyflakes
Change-Id: Ia96e701b80aa56223afd2b0c7956aea25b637942
Reviewed-on: https://chromium-review.googlesource.com/170025
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 10e992b5dd263d6bbb313655ef02f2e14893770d |
|
30-Aug-2013 |
Dan Shi <dshi@chromium.org> |
[autotest] Collect update engine log even if run_update failed.
BUG=chromium:279299
TEST=run_suite to force a machine install, interrupt the update by rebooting
DUT, confirm update_engine.log content is shown in autoserv.DEBUG
Change-Id: I97440face937a8c6bb4f009030aef01f02fe2f18
Reviewed-on: https://chromium-review.googlesource.com/167672
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 2f1ae9f1f2464ebbeb226a6669fa90ef211a179c |
|
13-Aug-2013 |
Chris Sosa <sosa@chromium.org> |
Add new files logic to devserver and clean up AU E2E test to use it.
There's a couple nested things here:
1) Pipe files through the autotest-side of the devserver logic. I've gone ahead
and added 5 unittests to test this new workflow with various combos of
artifacts. The main thing here is the optional pass of archive_url + files to
the stage_artifacts methods. I've also added a convenience function to return
the url to any staged file on the devserver if you know the filename (which you
would if you are using files= API).
2) Use the new logic in AU E2E API and figure out the right URL's to pass to
stage artifacts from. This was a bit of refactoring to get right.
In order to allow me to serve any artifact I had to change a bit of of the
source version installation logic to allow me to update from any static url
(rather than one that must end in update.gz). This actually makes the
OmahaDevserver much more flexible and more Omaha-y.
BUG=chromium:267896
TEST=Unittests + tested with both an nmo + npo full run.
Change-Id: Ic490c7c0e7d76eb8c0416accefbe113b9c0bba32
Reviewed-on: https://gerrit.chromium.org/gerrit/65732
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 03eaad90a2fabae6f3253e9acde8859681237610 |
|
26-Jun-2013 |
joychen <joychen@google.com> |
Update devserver urls with /archive in autotest(2)
[autotest] Remove archive from the devserver url patterns.
Devserver is removing static/archive so that everything is served
straight from the static directory. Cutting out calls in autotest to
match.
BUG=chromium:214373
TEST=Ran a suite with a reimage job on a DUT with the old
style job_repo_url.
Change-Id: Id3e2e0559c82a5424ef50406c7360ce28ca9a337
Reviewed-on: https://gerrit.chromium.org/gerrit/62918
Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org>
Commit-Queue: Joy Chen <joychen@chromium.org>
Reviewed-by: Joy Chen <joychen@chromium.org>
Tested-by: Joy Chen <joychen@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 458bf9ef5cf16bf88b306844a54d073c9cde5856 |
|
20-Jul-2013 |
Richard Barnette <jrbarnette@chromium.org> |
Revert "Update devserver urls with /archive in autotest."
This reverts commit f67d57a79eab93bf731f5bcf2a48fd04e3e08c68
This seems to be causing bugs in the test environment prior
to pushing to prod.
BUG=chromium:262279
TEST=see bug description
Change-Id: I79c300ad5647d283b862322e7ce29d8b7165766d
Reviewed-on: https://gerrit.chromium.org/gerrit/62708
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Joy Chen <joychen@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| f67d57a79eab93bf731f5bcf2a48fd04e3e08c68 |
|
26-Jun-2013 |
joychen <joychen@google.com> |
Update devserver urls with /archive in autotest.
Devserver is removing static/archive so that everything is served
straight from the static directory. Cutting out calls in autotest to
match.
BUG=chromium:214373
TEST=None
Change-Id: Iebc74469c93d0c95b676dcc45045dbcbd089efb5
Reviewed-on: https://gerrit.chromium.org/gerrit/60101
Commit-Queue: Joy Chen <joychen@chromium.org>
Reviewed-by: Joy Chen <joychen@chromium.org>
Tested-by: Joy Chen <joychen@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| ec1de4238e95356b80ff9b1d40695416ee47b2c9 |
|
27-Jun-2013 |
J. Richard Barnette <jrbarnette@chromium.org> |
Change update version checking when update_version is None
If a ChromiumOSUpdater instance is created with the
local_devserver=True option, the check_version_to_confirm_install()
method will always return False. In the case of a local
devserver, we want to skip the version test, so this changes
the method to always return True for the local devserver case.
BUG=None
TEST=run_remote_tests with autoupdate/control.local
Change-Id: Ie0790e0e1498aaf8c60a2275829a4cbd35de454a
Reviewed-on: https://gerrit.chromium.org/gerrit/60151
Reviewed-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 73aa2908e457c64ede3597cc78451cca5fba85be |
|
03-May-2013 |
Dan Shi <dshi@chromium.org> |
[Autotest] add support to check pgo-generate build
After a pgo-generate build is installed, lsb-release has version string like
'3837.0.0-pgo-generate', autoupdater needs to be updated to handle version
string in such form.
BUG=chromium:237803
TEST=local unittest, and try lumpy-release-pgo-generate/R28-4082.0.0
DEPLOY=none
Change-Id: I9548c430fa64998fe9965daa707f6a6606f9f783
Reviewed-on: https://gerrit.chromium.org/gerrit/50050
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 5002cfc325d4cf1a87553b427f972d2fd7bc6819 |
|
29-Apr-2013 |
Dan Shi <dshi@chromium.org> |
[Autotest] Remove empty space and tab in image url and version
scheduler may pass in an image option with \t at the end in autoserv command
line. The causes autoupdater failed to match the version from image or
update_version with lsb-release version string. The fix is to filter out any
tab and empty spaces in the beginning and end of image option for autoserv, as
well as in method autoupdater.url_to_version.
BUG=chromium:236382
TEST=local manual test
DEPLOY=none
Change-Id: Ideae45cd46c9cc34522fdf21aabaf067be9e6504
Reviewed-on: https://gerrit.chromium.org/gerrit/49495
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 7231260da421abdf5ceceff6ab60155936dca21f |
|
17-Apr-2013 |
Chris Sosa <sosa@chromium.org> |
Update the stateful partition during an update test.
For test images, we may need to update the stateful partition during
a test as Y may not be compatible with X. For example, we just got
burned with the Python2.6->Python2.7 upgrade where the new rootfs
symlinked /usr/bin/python to /usr/local/bin/python2.7 which doesn't
exist unless you update the stateful partition as well.
As part of this, I have exposed the stateful update from autoupdater
to make it easier to use. I have also added unittests for this method.
BUG=chromium:232085
TEST=pylint + manual
Change-Id: I6088cf671d090fca7aabff25335f4c0b8e3947c1
Reviewed-on: https://gerrit.chromium.org/gerrit/48331
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 7f79551b1fd8d8742b8d1013ceb5d023fec07f83 |
|
12-Apr-2013 |
Dan Shi <dshi@chromium.org> |
[Autotest] Correct version check for chrome-perf build.
Code is changed in check_version_to_confirm_install, so that special logic is
only applied to trybot paladin build. For any other build, the version without
any tail part (e.g., -rc#) is used to match the version in lsb-release.
BUG=chromium:230375
TEST=local unit test, run_suite with lumpy-chrome-perf/R28-3970.0.0-b2996
DEPLOY=none
Change-Id: I0283546a0b1d7f1036240bb6062d37b54ca53120
Reviewed-on: https://gerrit.chromium.org/gerrit/48016
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 190c780678495614cb477453d44cab6aefcfbe1e |
|
04-Apr-2013 |
Dan Shi <dshi@chromium.org> |
[Autotest] Correct version check for trybot release build
For release build, even trybot build has version string without the date
string. This CL checks if the image is a release build based on update_url
(looking for -release).
BUG=chromium:226120
TEST=manual test in local machine, try both paladin and release build from
trybot.
DEPLOY=none
Change-Id: I8776c2fbb24973c4c6f3055af705123e0deec14b
Reviewed-on: https://gerrit.chromium.org/gerrit/47349
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| b95bb86f445f886b3e66762c6b10686c52ffe905 |
|
23-Mar-2013 |
Dan Shi <dshi@chromium.org> |
[Autotest] Enable trying stateful update only in machine_install
The issue (222238) of version in /etc/lsb-release does not have the rc# was
fixed in CL https://gerrit.chromium.org/gerrit/#/c/46020/. Stateful update
only for DUT running image with same version is enabled. For trybot build,
machine_install will always do a full install, as cros version, e.g.,
3888.0.2013_03_21_1340, does not follow the same standard as paladin build,
e.g., 3888.0.0-cl2.
BUG=chromium:222098
TEST=manually run_suite in local machine, against following build:
trybot-lumpy-paladin/R27-3888.0.0-b711, lumpy-paladin/R27-3893.0.0-rc2,
lumpy-release/R27-3893.0.0
Change-Id: Ib0d558e760fdda975240fe9487417fed445be199
Reviewed-on: https://gerrit.chromium.org/gerrit/46330
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| eadbf7098c7cf810aaaf88791b1d59b786407e9f |
|
14-Mar-2013 |
Scott Zawalski <scottz@google.com> |
Modify our support of --image to work with our devservers.
Add a pathway to the --image code in site_host to stage anything that
is passed to it via --image that does not start with http://.
Added code to properly update job_repo_url in site_host rather
than in the try-jobs we spawn off. This makes it so that repaired
images as well as installs via --install have the proper job_repo_url
if they exist in the AFE.
Updated AfeClient.html to show examples of what can be specified in
Image Url.
Update old way of setting REPO URL in site_autotest.py to only be
used if someone is specifying a HTTP URL themselves, otherwise use the
AFE.
TEST=ran autoserv:
./autoserv --image=stumpy-release/R27-3836.0.0 -m scottz-stumpy1 -s
tests/sleeptest/control
and
./autoserv
--image=http://172.22.50.205:8082/update/stumpy-paladin/R27-3837.0.0-rc2
-m scottz-stumpy1 -s tests/sleeptest/control
and with a bad image which fails after a short while with an error about
the build path.
./autoserv --image=x86-mario-release/R27-3834.dd0.0 -m scottz-mario1 -s
tests/sleeptest/control
Test on a non-afe host:
./autoserv --image=x86-mario-release/R27-3834.0.0 -m 172.29.151.133 -s
tests/sleeptest/control
Tested repair update as well just to make sure I didn't break anything.
./autoserv -R -m scottz-mario1 # with a modification to make verify
fail always.
Ran tests through the frontend.
BUG=chromium-os:38653
Change-Id: I4b620a4332c695f4c972a8f8c112b4bf1dd6ba9a
Reviewed-on: https://gerrit.chromium.org/gerrit/45419
Tested-by: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Queue: Scott Zawalski <scottz@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 0f466e85d1c3fb7b9cd1b232a821b31ee58e4ff5 |
|
23-Feb-2013 |
Dan Shi <dshi@chromium.org> |
[Autotest] Update the Autotest installer code to avoid reinstalling the
same version
When a try job is started to install a new image in DUT, the DUT's version
is checked first. If the version is the same as the new image, machine_install
function in SiteHost first try to use stateful update to clean up the machine.
This is implemented by adding a new argument, update_root, in function
run_update in autoupdater. When update_root is False, autoupdater will only
do a stateful update, compared to updating kernel as well when update_root
is True. The main purpose for this change is to enhance the performance of
the try job on re-imaging.
BUG=chromium-os:31239
TEST=run_sutie against lumpy with smoke suite, try the command with same/
different version compared to what's running in DUT.
Change-Id: Ie358e7a5282f1fadefc26e78bbe4b38cd8e8fb8a
Reviewed-on: https://gerrit.chromium.org/gerrit/43851
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 0ed760cbee4ce839988585003d445465bb0b95b9 |
|
06-Nov-2012 |
Gilad Arnold <garnold@chromium.org> |
autotest: end-to-end autoupdate test
This implements an autotest test for the Chrome OS autoupdate
functionality. It receives a single test configuration and performs an
end-to-end test of the update process specified by it, which includes:
* Initializing the DUT to a known start state (source version)
* Spawning a local Omaha/devserver instance.
* Triggering an update process.
* Tracking the progress of the update.
* Rebooting the DUT after the update.
* Ensuring that the update has succeeded (target version running).
BUG=chromium-os:33760,chromium-os:33761,chromium-os:33762
TEST=Running with run_remote_tests.sh works
Change-Id: I215e8214d3239f525f062a27a4d97806451c9736
Reviewed-on: https://gerrit.chromium.org/gerrit/37432
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 7e437359e33429be6b7d25bc5ecf142beacab80a |
|
02-Nov-2012 |
Chris Sosa <sosa@chromium.org> |
Print out additional information when we fail to update.
We add crossystem debugging to what we print out on a failed
update check as well as cgpt show output.
BUG=chromium-os:35992
TEST=running
Change-Id: I681efc408aad64a59558127749340b341022b5e9
Reviewed-on: https://gerrit.chromium.org/gerrit/37294
Commit-Ready: Chris Sosa <sosa@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| a3ac2151472c3d8e569bc9166446807b231d5df0 |
|
24-May-2012 |
Chris Sosa <sosa@chromium.org> |
Modify autoupdate test to allow for local use by developers.
This change modifies the existing autoupdate test by adding
a local control file. Developers can use control.local to
run an autoupdate test from their local devserver.
BUG=chromium-os:31455
TEST=Ran it on a local eeepc with:
run_remote_tests --build autoupdate/
Change-Id: I5afb4eb74a943a62a8c1e2cc5365d0a910d63051
Reviewed-on: https://gerrit.chromium.org/gerrit/23469
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 5e4246b6dd51065cf4b0eebba333458d7ebf692c |
|
23-May-2012 |
Chris Sosa <sosa@chromium.org> |
Modify the autoupdater to reset the stateful update state on AU failure.
This change modifies the updater to reset the stateful update state
if an AU fails. This is needed so that we don't incorrectly continue
with a stateful update even when the rootfs fails to update.
CQ-DEPEND=I3dd6a29b087587c7557fa5a7968ebd48a52dd263
BUG=chromium-os:30795
TEST=Tested with local devserver and the rootfs update failing with
change I5afb4eb74a943a62a8c1e2cc5365d0a910d63051
Change-Id: I28b6b471ad5a05b6650ffd2608927ac8aa3bfd16
Reviewed-on: https://gerrit.chromium.org/gerrit/23304
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 77556d89a195ba3285c7701e60f63928188845ac |
|
06-Apr-2012 |
Chris Sosa <sosa@chromium.org> |
Re-land "Run the stateful update in parallel with the rootfs autoupdate.""
This reverts commit f52e79e13bd967668f7f7cf7c9b3ef538c29bb1f.
BUG=chromium-os:28751
TEST=Testing. Pyflakes, pylint + end to end run with cli/atest suite create
and a local devserver. Saw update complete and run bvt's.
Change-Id: I1cd16323b4f468afc6ee4abe4531babca8278f23
Reviewed-on: https://gerrit.chromium.org/gerrit/19700
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| f52e79e13bd967668f7f7cf7c9b3ef538c29bb1f |
|
05-Apr-2012 |
Scott Zawalski <scottz@chromium.org> |
Revert "Run the stateful update in parallel with the rootfs autoupdate."
This reverts commit 9bdcdf5b9f6b9398a05f3bc74f3a1c4f321b3d91
See bug: http://code.google.com/p/chromium-os/issues/detail?id=29025
Change-Id: Idd5517689c8f3b87fdb93a5b73a9c63410a5c78f
Reviewed-on: https://gerrit.chromium.org/gerrit/19688
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 4bd96d13d0ff7f6134a7ec4b35badf427965fa5a |
|
03-Apr-2012 |
Chris Sosa <sosa@chromium.org> |
Run the stateful update in parallel with the rootfs autoupdate.
BUG=chromium-os:28751
TEST=Testing. Pyflakes / pylint so far.
Change-Id: I53788dc277249096aa92c82fcf011dde419c2395
Reviewed-on: https://gerrit.chromium.org/gerrit/19491
Reviewed-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| d9b26b91061e9bd282d4104c4b17cfa7814e76ca |
|
24-Oct-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Fix partition rollback issues on update failure.
BUG=chromium-os:22006
TEST=Ran command.
Change-Id: I19475945e3b2a16fe03805630a5e56fcbbfb1923
Reviewed-on: http://gerrit.chromium.org/gerrit/10585
Reviewed-by: Darin Petkov <petkov@chromium.org>
Tested-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| ddfdb9491c7056d21163fc8d7f27d30e08794266 |
|
14-Jul-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Fix up autoupdate code to handle new AU format URLs.
Previously the target version was always the last element in the URL.
With AU format URLs, the target version is earlier in the URL. So strip
off the AU section before reading the path.
Also fixes Autoupdate control file so it properly generates failures
when an update fails.
BUG=chromium-os:16480
TEST=Ran run_remote_tests --update_url.
Change-Id: I126e3eb8a54eff31fae010793ff850af176763ff
Reviewed-on: http://gerrit.chromium.org/gerrit/4109
Reviewed-by: Paul Pendlebury <pauldean@chromium.org>
Tested-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 1e97318792dc35f1058772d5aa320573dd11d4da |
|
13-Jul-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Collect update engine logs on failure for debugging.
There are many instances where we need to check the update_engine logs
after a job has failed, but generally the machine has already been
reimaged by the time we notice a failure. Since the error occurs in the
install phase logs are never collected.
Instead of copying all logs, I've just made it so the update engine logs
and the latest messages file are retrieved. I chose to do it this way
since the system is in an unknown state prior to imaging, there could be
a large quantity of logs and crashes we aren't interested in. We can
re-evaluate this decision going foward if there's missing information.
BUG=none
TEST=Ran updater, killed update-engine, checked logs.
Change-Id: I1dba7d6016f4020c6173ae22db3a74af038d964a
Reviewed-on: http://gerrit.chromium.org/gerrit/3994
Tested-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Darin Petkov <petkov@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| f57a25f877842c88fd1109533ffaccab878c4bc1 |
|
24-May-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Improve update version checks to be more robust.
As an added bonus we can now support the new version scheme.
BUG=chromium-os:15706
TEST=Ran run_remote_tests --update_url.
Change-Id: Id644efdab571e01b69ffdb59486e775765518024
Reviewed-on: http://gerrit.chromium.org/gerrit/1483
Reviewed-by: Eric Li <ericli@chromium.org>
Tested-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 53d55866a9f977cc75d67db43d8a216ffbe5e7eb |
|
16-May-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Turn off forced updates. Modify perf to always update.
To increase lab efficiency we only want to trigger an update if we're
not already running the version we want to test.
However, some tests (boot perf) need to always start with a fresh
install.
BUG=none
TEST=Ran run_remote_tests --update_url w/ Old->New, New->New.
Change-Id: Ie5e1eee89f3c603938e24d6743d93f7cbdcbc544
Reviewed-on: http://gerrit.chromium.org/gerrit/943
Reviewed-by: Eric Li <ericli@google.com>
Tested-by: Eric Li <ericli@google.com>
Tested-by: Eric Li (do not use)
Reviewed-by: Eric Li (do not use)
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 5c32c72beab5784abff82d07bf2618946c2445ec |
|
05-May-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Cleanup and slight refactoring of autoupdater.
After having to test many autoupdate changes recently, I've run into a
few headaches which require some cleanup.
Most notably, the hack we use to make sure stateful_update is recent is
a PITA. I've changed this to fail quietly and fall back to whatever
version of stateful_update is available on the host.
I've also made some various code cleanups.
BUG=none
TEST=Ran run_remote_tests.
Change-Id: Iebbbe89ff8483f412f1ce489ab7a9b13c03f3e90
Reviewed-on: http://gerrit.chromium.org/gerrit/801
Tested-by: Eric Li(李咏竹) <ericli@chromium.org>
Reviewed-by: Eric Li(李咏竹) <ericli@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| b2cbc63a39708de594bbb3ed199daada697526d0 |
|
12-May-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Remove 2min delay after autoupdate.
http://crosbug.com/14954 is now fixed.
BUG=chromium-os:14954
TEST=none
Change-Id: I8f2473d18cae1dad1c1661334e09cfa483010adf
Reviewed-on: http://gerrit.chromium.org/gerrit/735
Tested-by: Eric Li(李咏竹) <ericli@chromium.org>
Reviewed-by: Eric Li(李咏竹) <ericli@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| a5b75c741c5d0fd13d7255373acd8a89e8eed7fb |
|
06-May-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Add two minute timeout after resetting update-engine.
Workaround for http://crosbug.com/14954
BUG=chromium-os:14954
TEST=Running in production.
Change-Id: Ieaee55465e2fb0cbce9d991076108b7305e5d4cb
Reviewed-on: http://gerrit.chromium.org/gerrit/403
Reviewed-by: Darin Petkov <petkov@chromium.org>
Tested-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| a94c19cab7ab15579a9d7bf96f2a61be29d534f7 |
|
03-May-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Add new update verifications per discussion with jrbarnette.
Per Richard:
1. Apply the update.
2. Determine the currently active kernel with 'rootdev -s': partition 3
-> KERN-A; partition 5 -> KERN-B.
3. Use 'cgpt show -P' to determine the priority of KERN-A (partition 2)
and KERN-B (partition 4).
4. Fail the test if the priority of the inactive root is not greater
than the priority of the active root.
5. Reboot the target.
6. Get the current software version from /etc/lsb-release.
7. Fail the test if the version from 6. doesn't match the expected
value.
8. Determine the currently active kernel again, as for step 2.
9. Fail the test if the currently active kernel isn't the new kernel.
10. Use 'cgpt show -S' and 'cgpt show -T' to determine the "tries" and
"success" flag values, respectively, for the currently active kernel.
11. Fail the test if (tries != 0 or success == 0) more than 60 seconds
after booting.
BUG=chromium-os:13761
TEST=Tested with autoserv --image on Mario.
Change-Id: Ieeca622edd0118690443f75c1e36a5ba2581e883
Signed-off-by: Dale Curtis <dalecurtis@chromium.org>
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 1f288ee1967599a36af5afc0b7f37b5f96ee616c |
|
15-Mar-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Add stateful partition reset to upgrade process.
The --stateful_change=clean flag is working again for stateful updates. By adding the flag to our upgrade process we ensure that we're always working with a clean base for testing. No more out of space issues due to lingering core dumps or other files.
Change-Id: Iee205df9964bef49f47422b13d2adcf1f38a9dd4
BUG=chromium-os:11971
TEST=Tested flag manually on ToT public, ToT mario, RC mario, and RC agz. Will test code in production.
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=85ce69e
Review URL: http://codereview.chromium.org/6021006
/external/autotest/client/common_lib/cros/autoupdater.py
|
| fb2b9f2c2a93db2093f5363a6650dd6b7a833e33 |
|
15-Feb-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Revert stateful_change=clean and timeout=120.
--stateful_change=clean is stil broken. The chrome startup scripts try to copy the stateful partition to /tmp before cleaning. Which would be great except /tmp is a tmpfs (memory-based) file system and our stateful partition is pretty big. sosa is working on a fix, until then these two commits need to be rolled back:
http://codereview.chromium.org/6021006/
http://codereview.chromium.org/6516017/
Change-Id: If40ebf939c2c183729a8299e0001bfb15cdf1295
BUG=chromium-os:11971
TEST=Running now on cautotest.
Review URL: http://codereview.chromium.org/6480053
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 85ce69e1fb0f400bf1374cac622350ee4a178dcf |
|
11-Feb-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Add stateful partition reset to upgrade process.
The --stateful_change=clean flag is working again for stateful updates. By adding the flag to our upgrade process we ensure that we're always working with a clean base for testing. No more out of space issues due to lingering core dumps or other files.
Change-Id: Iee205df9964bef49f47422b13d2adcf1f38a9dd4
BUG=chromium-os:11971
TEST=Tested flag manually on ToT public, ToT mario, RC mario, and RC agz. Will test code in production.
Review URL: http://codereview.chromium.org/6021006
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 793f912fe362a37125c4ef719debe35666c61987 |
|
05-Feb-2011 |
Dale Curtis <dalecurtis@chromium.org> |
Support dev builds.
First draft for this change. Depending on how we decide to archive dev builds this may change.
Change-Id: I4e167967e9c343d2582275075b8eb1291962a02f
BUG=chromium-os:11712
TEST=Ran w/ lab_test tool on cautotest.
Review URL: http://codereview.chromium.org/6312162
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 9da65c483ef9368379f8918c17fd4ede63b887cf |
|
07-Dec-2010 |
Eric Li <ericli@google.com> |
Revert "Revert "Create a cros directory under client, and start moving things into it.""
This reverts commit 985a034fc1fdec67841dd73d1913b0020e689423.
Resubmit http://codereview.chromium.org/5519008/
along with http://codereview.chromium.org/5568008/ this time.
Change-Id: I1b5b10ba3e4f9b13e0632cd45f27210bcb13b2a0
TBR=seano
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 985a034fc1fdec67841dd73d1913b0020e689423 |
|
07-Dec-2010 |
Sean O'Connor <seano@chromium.org> |
Revert "Create a cros directory under client, and start moving things into it."
This reverts commit 4b1222e930ef86507beb7232e7b7400d043f95ba.
Looks like something broke with autotest module imports in ericli's renaming CL.
the preflight smoke test complained:
Running client test client/site_tests/suite_Smoke/controceback (most recent call last):
File "./server/autoserv", line 35, in <module>
from autotest_lib.server import server_job, utils, autoserv_parser, autotest
File "/build/x86-generic/usr/local/autotest/server/server_job.py", line 11, in <module>
from autotest_lib.client.bin import sysinfo
File "/build/x86-generic/usr/local/autotest/client/bin/sysinfo.py", line 6, in <module>
"site_sysinfo", base_sysinfo.base_sysinfo)
File "/build/x86-generic/usr/local/autotest/client/common_lib/utils.py", line 1412, in import_site_class
res = import_site_symbol(path, module, classname, None, modulefile)
File "/build/x86-generic/usr/local/autotest/client/common_lib/utils.py", line 1376, in import_site_symbol
module = import_site_module(path, module, modulefile=modulefile)
File "/build/x86-generic/usr/local/autotest/client/common_lib/utils.py", line 1358, in import_site_module
return __import__(module, {}, {}, [short_module])
File "/build/x86-generic/usr/local/autotest/client/bin/site_sysinfo.py", line 5, in <module>
from autotest_lib.client.cros import constants as chromeos_constants
ImportError: No module named cros
BUG=
TEST=
Review URL: http://codereview.chromium.org/5592008
Change-Id: I440b4e1df68bad73d0592870653c94c55a1a6b8d
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 4b1222e930ef86507beb7232e7b7400d043f95ba |
|
07-Dec-2010 |
Eric Li <ericli@google.com> |
Create a cros directory under client, and start moving things into it.
The first step only includes chromeos_constants.py. But you get the idea how the others will look like.
Change-Id: I0a601a53e4d9a43f06e9f9f67429ac780f2562d0
BUG=7236
TEST=bvt test
I dont worry too much about occasional break ups caused by this, since I will continues working on this refactoring and this is just the beginning.
Review URL: http://codereview.chromium.org/5519008
/external/autotest/client/common_lib/cros/autoupdater.py
|
| 538b704621d22836e8e627b43f6df76408be3843 |
|
04-Dec-2010 |
Eric Li <ericli@google.com> |
This is the first CL to refactor autotest to move all cros related modules into a cros dir.
Change-Id: Ib729f30aea39f9fa6ba6519b5baec6babea1f01d
BUG=7326
TEST=run server/autoserv --image= with both client and server sleeptest.
Review URL: http://codereview.chromium.org/5626007
/external/autotest/client/common_lib/cros/autoupdater.py
|