Failures in AU OOBE test |
||
Issue descriptionThere are 3 different failures in the new AU OOBE test. 1. Not dealing with an expected update engine event (UPDATE_ENGINE_UPDATE_AVAILABLE). 2. Not waiting for the final update check after reboot before checking the hostlog of events. (Fails on slower machines) 3. OOBE not being ready. Seems to be only on slow machines so I'll increase the timeout
,
Dec 12 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/1433420e1d98305b5e713869bb6e38d636520ec8 commit 1433420e1d98305b5e713869bb6e38d636520ec8 Author: David Haddock <dhaddock@chromium.org> Date: Tue Dec 12 19:09:12 2017 [autotest] Fix failures in OOBE AU test. The AU OOBE test is failing for a few small issues that were missing in testing because I was only testing on a fast chromebook. This fixes a few failures that are occuring on slower machines. BUG= chromium:793922 TEST=test_that <ip> autoupdate_ForcedOOBEUpdate Change-Id: Iff33478f18a93cdc98d595bdd8d6ffc68c0d0c0b Reviewed-on: https://chromium-review.googlesource.com/820643 Commit-Ready: David Haddock <dhaddock@chromium.org> Tested-by: David Haddock <dhaddock@chromium.org> Reviewed-by: Vinayak Suley <vsuley@chromium.org> [modify] https://crrev.com/1433420e1d98305b5e713869bb6e38d636520ec8/server/cros/update_engine/omaha_devserver.py [modify] https://crrev.com/1433420e1d98305b5e713869bb6e38d636520ec8/client/site_tests/autoupdate_StartOOBEUpdate/autoupdate_StartOOBEUpdate.py [modify] https://crrev.com/1433420e1d98305b5e713869bb6e38d636520ec8/server/site_tests/autoupdate_ForcedOOBEUpdate/autoupdate_ForcedOOBEUpdate.py
,
Dec 15 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by dhadd...@chromium.org
, Dec 11 2017