New issue
Advanced search Search tips

Issue 845248 link

Starred by 2 users
Status: Assigned
Owner:
ahass...@chromium.org
Cc:
norvez@chromium.org
dhadd...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Add an autotest for failing delta updates

Project Member Reported by ahass...@chromium.org, May 21 2018 
If a delta update is failed for like 3 consecutive times, then a full update will be requested. Add an autotest that catch this situation and make sure we have some of it covered in the unittests. 

@dhaddock: Do you have such a autotest?

Comment 1 by dhadd...@chromium.org, May 21 2018 

Nope, we don't have a test for this. At the moment the only way we have for ensuring the update fails is to pull the network cable during the update and wait for update_engine to give up. Is there a better way?

Comment 2 by ahass...@chromium.org, May 22 2018 

For this specific case, what we can do is to restart the update engine service two or three times while it is delta updating so it will be considered as a failure (or reboot) and can punt to full update after that.

Comment 3 by dhadd...@chromium.org, May 24 2018 

OK cool. This may be hard to time with the N-to-N delta payloads though because they are tiny

Comment 4 by ahass...@chromium.org, May 29 2018 

The N-to-N delta payloads are tiny, but it still takes some time to install the payload which is around (or a bit more) the time it takes to install the full update.

Comment 5 by benhenry@chromium.org, Aug 3

Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
►

Sign in to add a comment