This reverts commit 2b2d7a1426.
The internal x86 buildbots have been reporting failures from
cros_au_test_harness with every build, starting with the build
that included the change being reverted.
BUG=chromium-os:8901
TEST=None
Review URL: http://codereview.chromium.org/5962019
Change-Id: Iac8c0a13d659f927b3ff61a9a894c10191432e2d
This cleanup code consolidates parsing of options, removes
globals, cleans up private vs. public functions, removes the backup full update option, and cleans up
docstrings.
Change-Id: I3eba26b3634fd87f4a36f195ab42ec7bd11e963f
BUG=chromium-os:8901
TEST=Ran with prefix SimpleTest and ran whole suite for a vm using my latest built image. Also ran normal update test using latest image against latest dev channel image for mario
Review URL: http://codereview.chromium.org/6015013
Change-Id: Ie80843a7b81a37b41ae19fc33244b5c0b8152282
BUG=chromium-os:10434
TEST=Ran it with full au test harness (still running but already showing promise).
Review URL: http://codereview.chromium.org/5988006
We had a major issue because the latest dev channel release pre-dates the virtio change. Because of this, ctest was connecting to update that channel using virtio (which is unsupported for that). This change drops a file telling the vm lib to use e1000 as before.
Also, fixed stateful change logic.
Change-Id: I394a8cece71bdd0d55efa21ba5b6d24804432c6b
BUG=chromium-os:10434
TEST=Ran it with ctest and cros_au_test_harness on images with/without the file.
Review URL: http://codereview.chromium.org/5928005
ability to filter or manipulate content as it's passed through.
Create two example tests using this utility that cause
updates to close early to test resumes, and to add delays
to make sure the update still completes correctly.
What other tests should be created for this?
BUG=chromium-os:8207
TEST=Run by hand
Review URL: http://codereview.chromium.org/5632002
Change-Id: Iefb8c8e223fb2ba6bad2c551f7c4403a0bec6ecf
Adds verbose flag to print output while updates are running rather than on error.
Adds test_prefix to specify a prefix of tests you want to run
Flushes stderr more reliably for builders and debugging purposes
Dies when stateful_updates fail
Change-Id: I9e4289deec3688c52b92763eee9334a8868f948e
BUG=chromium-os:6910
TEST=Ran with test_prefix and verbose on and off
Review URL: http://codereview.chromium.org/5573007
I started to use /tmp, but it doesn't exist both inside and outside of the chroot. Using a consistent name like this has the advantage that the files will be cached and not redownloaded every time. Well, except on the build servers that wipe the related directories between builds.
Change-Id: I58b42d9f1bd18cc4eb44043ed2436d4ffa482767
BUG=chromium-os:10012
TEST=
Review URL: http://codereview.chromium.org/5597004
Add two new tests that test update-engine handling of a corrupted image,
or a truncated image.
BUG=chromium-os:9502
TEST=Ran against Dell L13, Mario
Review URL: http://codereview.chromium.org/5373008
Change-Id: Ie1043004f01131ea837798c06327c486e1901c15
This would not have been a problem if "--no_graphics" is used.
Change-Id: I3645391d25d4bb8618109ff5be0ca2fbe8e96a60
BUG=chromium-os:9373
TEST=Ran by hand
Review URL: http://codereview.chromium.org/5104006
Currently works around issue till we get a good fix in for 9.x.
Change-Id: I9c7225508fa8f46a5fa5e0b41abc4e373cc80085
BUG=8606
TEST=Tested by sending SEGV to a delta update during update and saw it successfully fall back to a full update and succeed.
Review URL: http://codereview.chromium.org/4258002
BUG=8306
TEST=Ran au_test_harness with CL for adding vm option for the devserver on the last channel release and my TOT. All tests passed.
Review URL: http://codereview.chromium.org/4165009
Change-Id: Ia2ce305dff2911dc4008d5f6e383535e4bbd4ab0
Change-Id: Iabc931f2eb1751ca9d05e92e64e5361755791648
BUG=
TEST=Copied and pasted from other try/except
Review URL: http://codereview.chromium.org/4109006
1) image_to_vm aborts because e2fschk requires a terminal to
be connected in order to check whether or not you want to repair the fs. Since
we always want this to be true, set -p
2) Clean up test harness to only verify the number of tests that passed on the
base image are the same on the update back to. This is because older images
have many tests that fail. I leave 10% as a reasonable number to pass.
3) Redirect output from autotest in run_remote_tests to stderr so it gets
logged in a calling script that captures stdout.
Change-Id: If412274353683add20d136747113eb9c2bd41330
BUG=4690, 5533, 7287
TEST=Ran with internal tools for builders.
Review URL: http://codereview.chromium.org/3536018
Change-Id: I913acd95c49b1cf0fd666b49fb5ec1e24f0f83d1
BUG=7285
TEST=Ran through test against with two test images.
Review URL: http://codereview.chromium.org/3619009
Change-Id: I4afa86fa7a6b772124de56114910a1ca5e3d4511
BUG=
TEST=Ran through update harness code and ran loman.
Review URL: http://codereview.chromium.org/3612004
This harness has support for test on vm machines. It takes a base image and target image path, creates an update-enabled vm image from the base image and performs updates using cros_run_vm_update (vm wrapper around image_to_live). It uses --snapshot for updating vm's and keeps them on (like a real machine would) so that the VM image is clean on the next test.
The current check in has two test cases -- updates without clobbering the stateful partition and updates with clobbering the stateful partition.
Change-Id: I5406eadb39fa36601d17f8dd15625bd6a8b38c15
BUG=6911
TEST=Ran through tests.
Review URL: http://codereview.chromium.org/3554002
