New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 769337 link

Starred by 2 users

Issue metadata

Status: Started
Owner:
Last visit 15 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

factory: Better sync time goofy plugin

Project Member Reported by hungte@chromium.org, Sep 27 2017

Issue description

Continue work for https://chromium-review.googlesource.com/c/chromiumos/platform/factory/+/686335/

Stimim and I reviewed the time_sanitizer plugin and found that it's not enabled by default today (periodic=0) , and even if we enable it, it's still probably not very helpful.

Currently time sanitizer will try to reach factory server, and retry after periodic_secs, and will stop syncing if it has synced successfully one time.

However, for most factories, DUT will boot without network, and will only be connected for certain tests (for example sync_factory_server). This makes the sanitizer plugin useless because it's hard to set periodic_secs.

As a result, we think the plugin should be changed to wait until network is considered as available (should be notified instead of polling), start the sync, then stop.

Also, using htpdate is better than the poor python implementation.
 
Labels: Hotlist-GoodFirstBug
Owner: hsinyi@chromium.org
Assign to noogler for practice
Status: Started (was: Assigned)

Comment 4 Deleted

Comment 6 by hungte@chromium.org, Today (3 hours ago)

@hsinyi, is this completed?

Sign in to add a comment