Interrupt forced AU autotest in the middle |
|||||
Issue descriptionThe test team needs to do this manually for each new FSI. It involves manually editing files on the DUT and editing omaha configs to get the device to start a forced update. Once the update is started we perform these steps: Reboot Power off Pull network We want to ensure the the update continues after each interruption I want to add a test to remove the need to manually do this work any longer
,
Feb 14 2018
cc'd folks interested in this area as an FYI
,
Feb 14 2018
,
Feb 14 2018
If the goal is to see if force AU can be bypassed, I think you have to run this test multiple times(stress it out) since you can interrupt the update at various interval and may end up with different result?
,
Feb 23 2018
The goal of this test is to do what my testers are doing manually to interrupt it and see if the update completes. Bypassing was covered in issue 683424.
,
Feb 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/0bad4a3ed725fab8c2a3d5079a685866dd2aa31e commit 0bad4a3ed725fab8c2a3d5079a685866dd2aa31e Author: David Haddock <dhaddock@chromium.org> Date: Fri Feb 23 07:54:36 2018 Forced AU at OOBE with interruptions. This test interrupts the forced update at OOBE by 1. Rebooting 2. Pulling the network for a couple of minutes 3. Suspend/Resume the device. We want to ensure the device can continue with the update no matter what end users do to the DUT. The test team manually performs these steps during every new device FSI. This test will remove the need for any more manual forced update at OOBE testing. BUG= chromium:810153 TEST=autoupdate_ForcedOOBEUpdate.* passing Change-Id: I8e2a6c1ae8556f3afbcef4510e93fd87f2465ba4 Reviewed-on: https://chromium-review.googlesource.com/917651 Commit-Ready: David Haddock <dhaddock@chromium.org> Tested-by: David Haddock <dhaddock@chromium.org> Reviewed-by: Katherine Threlkeld <kathrelkeld@chromium.org> [add] https://crrev.com/0bad4a3ed725fab8c2a3d5079a685866dd2aa31e/client/site_tests/autoupdate_DisconnectReconnectNetwork/autoupdate_DisconnectReconnectNetwork.py [add] https://crrev.com/0bad4a3ed725fab8c2a3d5079a685866dd2aa31e/server/site_tests/autoupdate_ForcedOOBEUpdate/control.interrupt.full [modify] https://crrev.com/0bad4a3ed725fab8c2a3d5079a685866dd2aa31e/server/site_tests/autoupdate_ForcedOOBEUpdate/autoupdate_ForcedOOBEUpdate.py [add] https://crrev.com/0bad4a3ed725fab8c2a3d5079a685866dd2aa31e/client/site_tests/autoupdate_DisconnectReconnectNetwork/control
,
Feb 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/ea694f9215e33c5893fa43db8209a59109df0ca1 commit ea694f9215e33c5893fa43db8209a59109df0ca1 Author: David Haddock <dhaddock@chromium.org> Date: Fri Feb 23 07:54:21 2018 Add autoupdate_DisconnectReconnectNetwork to ebuild. BUG= chromium:810153 TEST=None Change-Id: I655550f66f0f3f06b926a8197ed6696c67705b13 Reviewed-on: https://chromium-review.googlesource.com/917650 Commit-Ready: David Haddock <dhaddock@chromium.org> Tested-by: David Haddock <dhaddock@chromium.org> Reviewed-by: David Haddock <dhaddock@chromium.org> [modify] https://crrev.com/ea694f9215e33c5893fa43db8209a59109df0ca1/chromeos-base/autotest-tests/autotest-tests-9999.ebuild
,
Feb 26 2018
,
Dec 7
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dhadd...@chromium.org
, Feb 14 2018