This changes the behavior of ctest to try to grab the latest zip from the zip web pages if it can't use the latest link (due to IOError or none provided). It assumes they have an Apache server and they reference images using version->ChromeOS-version-.*.zip) for each board/channel.
Change-Id: I4ee075db7afd58c8d08f59aca2e69b5bab5ff5e9
BUG=7675
TEST=Ran it with -l "http://Doesnotexist" and also without a -l option. Added new unittests to test and ran them as well.
Review URL: http://codereview.chromium.org/3659002
The "emerge" process sometimes copies files to /var/tmp
and then run it. Recent changes to images set the
"noexec" flag on /var, thus preventing such activities.
Temporarily clear this flag from within cros_package_to_live.
BUG=none
TEST=Manually set noexec on /var and run cros_package_to_live
Review URL: http://codereview.chromium.org/3739001
In order to more easily test kernel commandline tweaks, ensure that
--boot_args is propagated to all kernel cmdline sinks.
This is useful for changing default schedulers and any other kernel argument
tweaks we may want to quickly test out.
TEST=build and tested x86-generic
BUG=none
Change-Id: I5138755aa8c5e32e7f117f18291d2ae197e95bef
Review URL: http://codereview.chromium.org/3644004
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: I4de388bb1af6cd4568cdc154971927941eb73800
BUG=7503
TEST=Ran test by closing vm's as they start up to see retry work.
Review URL: http://codereview.chromium.org/3598019
Change-Id: I913acd95c49b1cf0fd666b49fb5ec1e24f0f83d1
BUG=7285
TEST=Ran through test against with two test images.
Review URL: http://codereview.chromium.org/3619009
Change-Id: I01d613527777098616e8d5bd2b4b27bce240c02f
BUG=
TEST=Ran cbuildbot and prematurely killed autotest to show test failure. CBuildbot fails saying that cros_run_vm_test smoke_Suite failed.
Review URL: http://codereview.chromium.org/3517010
This will allow dev who didn't build an image to still use cros_make_image_bootable
to update their image -- including mod_image_for_test / image_to_vm.
Change-Id: I1ba4292223b28b21d5416745e7744641100fa4ad
BUG=7370
TEST=Ran image_to_vm with other image and image I built myself. Also ran
cros_make_image_bootable directly on a the same two images.
Review URL: http://codereview.chromium.org/3569015
Change-Id: I4afa86fa7a6b772124de56114910a1ca5e3d4511
BUG=
TEST=Ran through update harness code and ran loman.
Review URL: http://codereview.chromium.org/3612004
This script had a short painful life, constantly being brittle
and broken. It is time for it to go. Please use
cros_image_to_target.py instead.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/3536002
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
Right now we're leaving error_ok=True until the tests are shown to work on builder.
Change-Id: I6b8c690a0da30948389fd4312032c78d87115364
BUG=6906
TEST=Ran through it locally.
Review URL: http://codereview.chromium.org/3591002
- I looked at all of the x86 and ARM paths through out build image scripts,
these changes clean up stale comments, stale code, and unforks some small
things.
BUG=none
TEST=Built images for x86-generic, arm-generic and tegra2-seaboard, booted tegra2-seaboard image.
Review URL: http://codereview.chromium.org/3448022
Change-Id: Ibad2774ff2cbf5f15528454506542b87e43e24a2
Also fixed get latest image logic in image_to_vm and allowed for using the most recent image in cros_run_vm_test to follow other shell convention of using latest.
Change-Id: I60ed4c03d609500da7f6ae34ef57ba2e32f4b0bb
BUG=
TEST=Tested by running image_to_vm with --full and cros_run_vm_test with suite_Smoke
Review URL: http://codereview.chromium.org/3597001
If cbuildbot.py printed out a manifest when it syncs, it would make it possible
for us to reproduce the build later by looking at what revisions the buildbot
was using. This is useful for debugging.
Change-Id: I186ad01eef0090b6c618cb7ad583085197474018
BUG=chromium-os:7069
TEST=Ran test suite with 3441027 patched in (Sosa's patch that fixes an unrelated issue with the unit tests)
Review URL: http://codereview.chromium.org/3461028
repo sync --jobs doesn't check for errors, so we shouldn't use it in
automated scripts. repo --trace is needed so that we can diagnose
whether git is hanging.
BUG=chromium-os:7048, chromium-os:6774
TEST=Ran test suite
Change-Id: I9e68cfffe841a231f5fabef951ea2d45b81c1d5e
Review URL: http://codereview.chromium.org/3419024
This is needed in order to do the right thing when adding projects
which require a revision attribute.
BUG=6811
TEST=Updated unittests and verified they pass.
Verified that I can add chromeos-kernel-next and revision gets set.
Change-Id: I12818dad464094cd50098170da3fcf38b1e32f17
Review URL: http://codereview.chromium.org/3400019
- This unbreaks the devserver's update server for ARM.
- This also unforks some of build_image.
BUG=None
TEST=Installed to tegra2_seaboard from USB without --skip_vblock,
updated tegra2_seaboard.
Review URL: http://codereview.chromium.org/3493004
Change-Id: I6e66344de51609393407934f78aa20f49974efef
BUG=
TEST=Tested by persisting, ctrl+c, continuing and using same vm.
Also without --persist
Review URL: http://codereview.chromium.org/3419014
Change-Id: I49e26eb86101e8b8b50e58a9f277d62d5fadc664
restart_inside_chroot first assumes that the calling script is in
src/scripts. Next any paths are not converted when passed so if
someone passes the most recent image, this will also not be interpreted
correctly.
Change-Id: Icb2dfc661eb84e134b4d8c5cf0354a6c1ab161f0
BUG=
TEST=Manually tested running outside chroot (getting error) and inside chroot.
Review URL: http://codereview.chromium.org/3421025
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
The RF testbed has hosts behind a one-way firewall, so the
conventional "image_to_live" script does not work. My initial
attempt at solving this, 'cros_copy_upgrade_server', while
sometimes functional, was always quite brittle since it had
widely ranging dependencies which often changed in ways that
the authors could not predict would break our setup.
I've written from scratch a new script in python which uses
ssh tunnels to get around the problem of the firewall issue.
It also has retlatively minimal dependencies (stateful_update,
cros_generate_update_paylod, cgpt, get_latest_image.sh and
the testing keys) so hopefully it won't get blown away too
often.
BUG=none
TEST=Ran under chroot -- Need help testing
Review URL: http://codereview.chromium.org/3391008
Optionally disable mount/remount during package install for
targets that are already mounted read-write.
BUG=none
TEST=rerun
Review URL: http://codereview.chromium.org/3439012
- Build a "kernel image" which contains a uboot script and a uboot kernel
image.
- Fix some sd* assumptions.
- Remove cruft that has never done anything usefull from update_bootloaders
BUG=none
TEST=Built, booted, and updated on tegra2_dev-board
Review URL: http://codereview.chromium.org/3396011
Change-Id: I00ecf57faa5fe64c8e33dd4c042f1dbed806c10a
zbehan's change: "run_remote_tests: destroy the with_spaces hack,
use the --args instead of -a (which doesn't work)", despite apparently
not working is in active use by others, both by folks using it on the
command line and by the script cros_run_wifi_tests.sh. Fix the script
to match the new argument.
BUG=none
TEST=rerun
Review URL: http://codereview.chromium.org/3444010
cros_copy_upgrade_server can now start the devserver with either prefix.
This is to help the migration from Memento to ChromeOSUpdateEngine.
BUG=none
TEST=none (yet)
Review URL: http://codereview.chromium.org/3304013
Change-Id: Id81fe4e7bd9cae7a51a45b6ea8a535c4ea9430f8
BUG=
TEST=Ran locally on top of previous build area.
Review URL: http://codereview.chromium.org/3337007
Change-Id: I758c93596d5cbdd6b52b9acc82f4d6e19a326c9f
BUG=5518
TEST=Tested using all the options. All tests listed in the file pass.
Review URL: http://codereview.chromium.org/3107039
