New issue
Advanced search Search tips

Issue 613765 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: ----

Blocked on:
issue 633280
issue 636467

Blocking:
issue 608580



Sign in to add a comment

Add APIs in devserver

Project Member Reported by xixuan@google.com, May 21 2016

Issue description

As the second step of BUG:608580, creating several APIs in devserver to support function: cros auto-update.

These API includes:
1. an update API, support 'start cros auto-update', initialize a background thread to do cros auto-update.
2. an check API, to check the status of the thread of 'updating', and return back to drone/shard.

 

Comment 1 by xixuan@chromium.org, May 21 2016

Blocking: 608580
Owner: xixuan@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 2 2016

Labels: Hotlist-Google
Components: -Infra Infra>Client>ChromeOS
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 26 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/dev-util/+/52c2fba79e77ccd60dc4e01a66539bc3237277fb

commit 52c2fba79e77ccd60dc4e01a66539bc3237277fb
Author: xixuan <xixuan@google.com>
Date: Sat May 21 00:02:48 2016

dev: add initial APIs to devserver to support cros auto-update.

This CL adds three APIs on devserver:
1. 'cros_au' API: to support 'start cros auto-update'.
2. 'get_au_status' API: to check the status of cros auto-update.
3. 'collect_au_log' API: to collect auto-update log from devserver.
4. 'handler_cleanup' API: delete the status file for tracking the progress of
   CrOS auto-update.
5. 'kill_au_proc' API: to kill unexpected auto-update process for DUT.

Also it updates the unittests and integration test.

The 'cros_au' API triggers a background process to support the whole
auto-update processes for a CrOS host, includes:
1. Transfer devserver/stateful update package.
2. If devserver cannot run on the host, restore the stateful partition.
3. If restore_stateful_partiton is not required, and stateful_update is
required, do stateful_update.
4. If stateful_update fails, or rootfs_update is required, do rootfs update.
5. Final check after the whole auto-update process.

BUG= chromium:613765 
TEST=Locally ran 'ds.auto_update([dut], [image_path])';
Ran 'repair' for dut from local autotest instance;
Ran unittest, devserver_integration_test.

 Changes to be committed:
	modified:   Makefile
	new file:   cros_update.py
	new file:   cros_update_logging.py
	new file:   cros_update_progress.py
	new file:   cros_update_unittest.py
	modified:   devserver.py
	modified:   devserver_integration_test.py

Change-Id: I2e9c116bc1e0b07d37b540266fd252aee4fd6e84
Reviewed-on: https://chromium-review.googlesource.com/346199
Commit-Ready: Xixuan Wu <xixuan@chromium.org>
Tested-by: Xixuan Wu <xixuan@chromium.org>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>

[modify] https://crrev.com/52c2fba79e77ccd60dc4e01a66539bc3237277fb/devserver_integration_test.py
[add] https://crrev.com/52c2fba79e77ccd60dc4e01a66539bc3237277fb/cros_update_progress.py
[modify] https://crrev.com/52c2fba79e77ccd60dc4e01a66539bc3237277fb/Makefile
[add] https://crrev.com/52c2fba79e77ccd60dc4e01a66539bc3237277fb/cros_update_unittest.py
[add] https://crrev.com/52c2fba79e77ccd60dc4e01a66539bc3237277fb/cros_update_logging.py
[modify] https://crrev.com/52c2fba79e77ccd60dc4e01a66539bc3237277fb/devserver.py
[add] https://crrev.com/52c2fba79e77ccd60dc4e01a66539bc3237277fb/cros_update.py

Blockedon: 633280

Comment 6 by xixuan@chromium.org, Aug 10 2016

Blockedon: 636467
Status: Fixed (was: Assigned)

Comment 8 by dchan@chromium.org, Oct 7 2016

Labels: VerifyIn-55

Comment 9 by dchan@chromium.org, Oct 10 2016

Labels: -VerifyIn-55

Comment 10 by dchan@google.com, Nov 19 2016

Labels: VerifyIn-56

Comment 11 by dchan@google.com, Jan 21 2017

Labels: VerifyIn-57

Comment 12 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 13 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 14 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61
Status: Verified (was: Fixed)
Closing. Please reopen it if its not fixed. Thanks!

Sign in to add a comment