[CrOS Tether] Update the KeepAliveTickle code to receive DeviceStatus updates.

[CrOS Tether] Update the KeepAliveTickle code to receive DeviceStatus updates.

This CL consists of three parts:
(1) Update KeepAliveOperation to receive a KeepAliveTickleResponse message after sending a KeepAliveTickle message.
(2) Update KeepAliveScheduler to handle a received message and record the updated information in HostScanCache.
(3) Integrate KeepAliveScheduler into the app (i.e., initialize it in Initializer).

BUG=672263
Review-Url: https://codereview.chromium.org/2918863002
Cr-Commit-Position: refs/heads/master@{#477362}
Committed: https://chromium.googlesource.com/chromium/src/+/c2d14083b36f8b4bd8caf9031ae2ef6583d4e280

[Kyle Horimoto, 2017-06-01 21:38:51]

khorimoto@chromium.org changed reviewers:
+ hansberry@chromium.org

[Ryan Hansberry, 2017-06-01 23:45:52]

Please confirm that this works on a real device. Otherwise, lgtm.

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
File chromeos/components/tether/keep_alive_operation.h (right):

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
chromeos/components/tether/keep_alive_operation.h:40: // |device_status| point
to a valid DeviceStatus if the operation completed
nit: points*

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
File chromeos/components/tether/keep_alive_operation_unittest.cc (right):

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
chromeos/components/tether/keep_alive_operation_unittest.cc:57: DeviceStatus
CreateFakeDeviceStatus() {
Has this been copied from somewhere? If so, can we make this a general test
object?

[Kyle Horimoto, 2017-06-06 18:30:34]

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
File chromeos/components/tether/keep_alive_operation.h (right):

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
chromeos/components/tether/keep_alive_operation.h:40: // |device_status| point
to a valid DeviceStatus if the operation completed
On 2017/06/01 23:45:51, Ryan Hansberry wrote:
> nit: points*

Done.

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
File chromeos/components/tether/keep_alive_operation_unittest.cc (right):

https://codereview.chromium.org/2918863002/diff/20001/chromeos/components/tet...
chromeos/components/tether/keep_alive_operation_unittest.cc:57: DeviceStatus
CreateFakeDeviceStatus() {
On 2017/06/01 23:45:52, Ryan Hansberry wrote:
> Has this been copied from somewhere? If so, can we make this a general test
> object?

Done.

[Kyle Horimoto, 2017-06-06 18:30:38]

The CQ bit was checked by khorimoto@chromium.org

[Kyle Horimoto, 2017-06-06 18:30:38]

The patchset sent to the CQ was uploaded after l-g-t-m from
hansberry@chromium.org
Link to the patchset: https://codereview.chromium.org/2918863002/#ps40001
(title: "hansberry@ comments.")

[commit-bot: I haz the power, 2017-06-06 18:31:13]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-06 19:13:37]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1496773838250980,
"parent_rev": "3737d9dc0a52a4a3ce1692059a9d304e5b5436d1", "commit_rev":
"c2d14083b36f8b4bd8caf9031ae2ef6583d4e280"}

[commit-bot: I haz the power, 2017-06-06 19:13:47]

Description was changed from

==========
[CrOS Tether] Update the KeepAliveTickle code to receive DeviceStatus updates.

This CL consists of three parts:
(1) Update KeepAliveOperation to receive a KeepAliveTickleResponse message after
sending a KeepAliveTickle message.
(2) Update KeepAliveScheduler to handle a received message and record the
updated information in HostScanCache.
(3) Integrate KeepAliveScheduler into the app (i.e., initialize it in
Initializer).

BUG=672263
==========

to

==========
[CrOS Tether] Update the KeepAliveTickle code to receive DeviceStatus updates.

This CL consists of three parts:
(1) Update KeepAliveOperation to receive a KeepAliveTickleResponse message after
sending a KeepAliveTickle message.
(2) Update KeepAliveScheduler to handle a received message and record the
updated information in HostScanCache.
(3) Integrate KeepAliveScheduler into the app (i.e., initialize it in
Initializer).

BUG=672263

Review-Url: https://codereview.chromium.org/2918863002
Cr-Commit-Position: refs/heads/master@{#477362}
Committed:
https://chromium.googlesource.com/chromium/src/+/c2d14083b36f8b4bd8caf9031ae2...
==========

[commit-bot: I haz the power, 2017-06-06 19:13:50]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/c2d14083b36f8b4bd8caf9031ae2...