Change-Id: I8233aaab234eb6a3a7948abb1d311c4c9c162190
BUG=chromium-os:11172
TEST=Ran from new symlinks from previous locations.
Review URL: http://codereview.chromium.org/6731005
Change-Id: I2f741d7866192300946299f9050717721c2a644d
BUG=chromium-os:12605
TEST=Changed impl of check_status to return 1 and made sure timeout got inc'd
correctly and aborted. Also checked to make sure if status returned 0 i.e.
update_engine_client --status returned 0, we would continue.
Review URL: http://codereview.chromium.org/6594089
BUG=chromium-os:5246
TEST=below, During all tests, the directory platform/dev was manually removed
1) Ran cros_au_test_harness.py and saw it succeed
2) Ran generate_au_zip.py, compared the generated .zip with one before this
patch - they were identical
3) Ran cros_image_to_target.py and saw it succeed
Change-Id: Iab2620245a45442b79ee8369f3af1a3990f4644e
Review URL: http://codereview.chromium.org/6576023
from within the chroot.
It also fixes a number of style issues.
It changes the meaning of cros_workon "list-all" to list all available
packages, and adds "list-live" to list all live packages.
It changes things that load chromeos-common.sh from the installer to
load it from /usr/lib/installer.
BUG=chromium-os:4230
TEST=synced, rebuilt chroot, made packages, made images, built chrome
from source, and wrote an image to a USB stick.
Review URL: http://codereview.chromium.org/6240018
Change-Id: I90c34420af1a64020402bafef8e9e77f56837c02
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=c418a8f
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=be787f3
Review URL: http://codereview.chromium.org/6277015
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=c418a8f
Review URL: http://codereview.chromium.org/6277015
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Review URL: http://codereview.chromium.org/6277015
This CL also fixes the outstanding issue where to won't report progress in
image_to_live on updates.
Change-Id: I1efaf17f0fd5ebb367ae0872377b4d5d0bf5dbf6
BUG=chromium-os:8680,chromium-os:8901
TEST=Ran it with --debug on the x86 pfq locally.
Review URL: http://codereview.chromium.org/6135002
Without this, image_to_live can sometimes think that an update from the same version to same version worked when it failed.
BUG=chromium-os:9002
TEST=By hand (hardware && success only)
Review URL: http://codereview.chromium.org/6045004
Change-Id: Ic0835372a45a45785e21ba1527d478f447bcf42a
This change will not work properly unless the chroot sudo is
updated to handle escaping properly:
http://codereview.chromium.org/5923001
...and the chroot sudo will break image_to_live unless this
change goes in. Thus, the two changes are intertwined.
Change-Id: Ib1602ee47178fc5d32c286e9a914111c1140252b
BUG=chromium-os:7072
TEST=Valided that the dev server seemed to be getting proper args.
Review URL: http://codereview.chromium.org/5929001
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
This command can be used to update the kernel of a ChromiumOS target.
Much thanks to snanda for the inspiration and instructions.
BUG=9864
TEST=Verified that it works.
Change-Id: I66f7d940e0dc59b0e1a50409a7155fe0ba7157fe
Review URL: http://codereview.chromium.org/5550001
Change-Id: Ib366064df269bd0d4aee30e5b1628938bd8fedf9
BUG=8313
TEST=Running it once without passing an image
Review URL: http://codereview.chromium.org/4208003
Change-Id: I339e1ce3d8f73e15aa554e1111aced163819ec23
BUG=8732
TEST=Ran with other CL and using latest image.
Review URL: http://codereview.chromium.org/4527001
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: I4a6fc66db7b336ae07bdfa837dd5e0d806880e52
BUG=8255
TEST=Ran it with devserver with option.
Review URL: http://codereview.chromium.org/4169006
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: I0bcc3dbbf72fbae4bfa11340831d60d28202bb88
BUG=
TEST=Ran with just --remote=... to pick up latest image and it verified.
Review URL: http://codereview.chromium.org/3609003
Change-Id: I63bdcaa3630c179d407310f6544c102f5353fa4d
BUG=5530
TEST=Ran both cros_run_vm_test and new script and had the latter update successfully.
Review URL: http://codereview.chromium.org/3427011
Before this change, image_to_live could only be used by either passing a custom URL
or using the latest built image. I've added the following:
- Ability to update from an image.zip
- Ability to update from a specific image.
- Ability to clobber the stateful partition after an update
(excluding /usr/local and /var)
- Ability to customize and capture both the update and devserver logs.
- Ability to see the progress of an update.
I've also modified the start logic. It seems the update_engine can get in a state
where if you fail a previous update by killing the devserver, the update engine
will hang for a long time (retries a lot). So I've changed the behavior of
startup and detecting that the system isn't ready to update, to be, reboot and
then try the update.
BUG=
TEST=Tested with all options.
Review URL: http://codereview.chromium.org/3389009
Change-Id: I9bb42edbf5338385f55db242665c94cd552ab277
I've modified image_to_live to convert the dev server url into the proper form to access the stateful.image.gz and pass it along to stateful_update on the remote system.
Change-Id: I77971c83b7efef5f053fda7fcd2585ca73f3134a
BUG=6705
TEST=Imaged several machines using Dev Server.
Review URL: http://codereview.chromium.org/3417001
Change-Id: Iddc1a4c1fe83877eff020f3e075ddba5e5594a57
BUG=
TEST=Tested with new dev server changes. Ran through a successful update.
Review URL: http://codereview.chromium.org/3358004
BUG=4887
TEST=tested run_remote_tests and image_to_live still work. Ran script with machine with no crashes, as well as on a machine with a slew of powerd CHECK(false)'s.
Change-Id: Iffb6571d30d99d876f41972f92a7149a716035ee
Review URL: http://codereview.chromium.org/3276002
The issue here is if an previous update succeeded but reboot not happen, for what ever unknown reason, this host lost the ability to update again.
I think some of the current update failure in the lab should be caused by this.
Review URL: http://codereview.chromium.org/2031002
TEST=Tested with image_to_live, memento_updater without image_to_live
This mimics the update process of the real image for the stateful partition.
By moving this the update into a separate script, I can add it to the gmerge
package such that developers will not have to use image_to_live. This change
also removes the dependency on tar.
Review URL: http://codereview.chromium.org/1774021
TEST=Tested by running image_to_live with correct formated images as well
as images that are missing either /var or dev_image directories.
Review URL: http://codereview.chromium.org/1705023
2. I dont fully understand why we need sudo inside this script. So I am removing it. Since I could not enter sudo password inside crontab. Please let me know if I missed anything and I could revert.
Review URL: http://codereview.chromium.org/666002
Run a basic check on a buildbot grabbed image to make sure it has a
kernel installed in it.
Better failure recovery.
Review URL: http://codereview.chromium.org/553063
image_to_live.sh - fix problem where errorvalue is non-zero even when
reimage was successful.
run_remote_tests.sh - add ability to stow build description in the
autotest database so we can track the exact build for which
tests succeed/fail.
Review URL: http://codereview.chromium.org/547018
