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
Mark all ebuilds in chromiumos-overlay and chromeos-overlay as stable and
point them at the current version we have checked out.
This is useful in case we want to verify that all ebuilds are pointing at the
right commit hash when we are doing a build on a branch. It is intended to be
used prior to tagging and can be used instead of a preflight queue. It is an
alternative to cros_mark_all_as_stable that does not require a chroot and
does not increase the revision number on ebuilds.
Unlike cros_mark_all_as_stable, which only updates the latest stable ebuild
for a given board, this script updates all stable ebuilds for all boards,
including unused stable ebuilds. We do this for the sake of simplicity
because it's hard to know in advance which ebuilds are truly unused, and it
shouldn't hurt to update unused ebuilds.
This script does not support cros_mark_as_stable_blacklist. If there are any
packages in the blacklist, this script exits with an error message.
TEST=Ran this script to point power_manager at branch and tested that we
built power_manager from the branch.
BUG=chromium-os:7218, chromium-os:6429
Change-Id: Ib2308806c5a4db979b1245a90407fd5b6353e4fd
Review URL: http://codereview.chromium.org/3607014
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
cros_mark_as_stable.py was updated on Sep 8, but the unit test was not updated
to match. This patch fixes the unit test.
BUG=chromium-os:7586
TEST=Ran unit test.
Change-Id: I283ef33e172a95efc41b4090dc4f67c9d84dd9a3
Review URL: http://codereview.chromium.org/3682003
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: I51df060627770d88c219501bc628e91229ac0d42
BUG=7286
TEST=Boot in mod_for_test, home is mounted exec
Review URL: http://codereview.chromium.org/3529021
Change-Id: I636f3156e549508230515174edffaff650c9d46e
BUG=chromium-os:6759
TEST=(1)manually built a non-developer recovery image and verified recovery install
completes on an agz device and the device is able to boot from HD upon reboot
(2) repeat for a developer recovery image and verified dev image from dev_payload is installed onto target and the target is able to boot from HD
Review URL: http://codereview.chromium.org/3391018
A corresponding CL adds support for the delta generator to generate
new style full updates. This CL adds support for creating new style
full updates to the common update payload generator script.
This does not change the defaults, so generating a full update still uses
the old style.
BUG=7248
TEST=generated/applied full update on host
Review URL: http://codereview.chromium.org/3604011
Adding "-B 4m" to balance pipe (+10% speed on some SD) and -b to make progress more readable.
Since the size report from pv (k=1024) and dd(k=1000) are different, we also disable dd's summary report to prevent confusion.
BUG=none
TEST=executed: ./image_to_usb.sh --from=... --to=/dev/sdX (ok)
Change-Id: I184c4ce2d9a8274079ddb26f0420ccf8f2a674dd
Review URL: http://codereview.chromium.org/3608013
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: I0bcc3dbbf72fbae4bfa11340831d60d28202bb88
BUG=
TEST=Ran with just --remote=... to pick up latest image and it verified.
Review URL: http://codereview.chromium.org/3609003
Change-Id: I913acd95c49b1cf0fd666b49fb5ec1e24f0f83d1
BUG=7285
TEST=Ran through test against with two test images.
Review URL: http://codereview.chromium.org/3619009
This changes defaults failure to a panic/recovery reboot and
disables the debugging max_bios argument to ensure that we don't
trigger race conditions in the kernel during un-protected
pending_bio count decrements. (Can lead to a hung-system.)
TEST=built x86-generic; ensured -1 and the panic changes worked
BUG=chromium-os:6956
Review URL: http://codereview.chromium.org/3595015
Change-Id: I81c9e1a7f406e551cd528d5226902c89165b30f9
I've cleaned up parallel_emerge to send explicit signals to children to tell
them when they need to exit. I also cleaned up the CTRL-C handling to
correctly print data when interrupted by CTRL-C (previously, the print
thread exited first, so the data we wanted on the failure wasn't
actually printed.)
BUG=chromium-os:5976
TEST=Test several board emerges, including exiting early with CTRL-C.
Change-Id: Iab6efc8e1bf868106244a6210bd02e9e8283af37
Review URL: http://codereview.chromium.org/3534006
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
Change-Id: I1ad0aaec6517758812bf4ba0460ab0c81a6f84cb
BUG=7357
TEST=run_remote_tests.sh ... bvt regression and then observer both bvt and regression test result
Review URL: http://codereview.chromium.org/3603012
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
image_to_usb has been made to work inside chroot for quite some time
(maybe since http://codereview.chromium.org/1991006), and some special
modes may even require it to be executed inside chroot.
However the output messages were not fixed, so we should remove the
"OUTSIDE CHROOT" alerts.
BUG=none
TEST=manually:
1. executed build_image and verified that output messages is correct, and the image is really built successfully.
2. executed image_to_usb.sh --from=... --to=/dev/sde and verified output messages is correct, and the USB device is really imaged by the given target
Change-Id: I8f4274c5f59a0aa585471469ac285e91c0cead13
Review URL: http://codereview.chromium.org/3519003
BUG=none
TEST=run from within and without a repo
Change-Id: I00eb999974656450f6af24583ca2247805b5799e
Review URL: http://codereview.chromium.org/3529005
1. add oflags=sync to allow interrupting dd without hanging system I/O for a long time
(since bs=4M, the speed is almost the same)
2. use pv to provide progress report if available.
(add pv into host-depends in http://codereview.chromium.org/3608004)
BUG=none
TEST=manually:
1. install pv in chroot, then execute image_to_usb.sh --to /dev/sdX and verified there's progress bar
2. ctrl-c to break the dd process and verified it can stop immediately
3. remove pv from chroot, then execute image_to_usb.sh and verify that it still works
Change-Id: I62fc373a4feee6d7e61897325d9e1e6d84a74d63
Review URL: http://codereview.chromium.org/3581007
This introduces a way to upload prebuilts from the command line.
The following features are available
* Multiprocess upload (cuts time down by a 1/5th for uploading)
* Versioned uploading with git file commital
* Host prebuilt uploading
* Board prebuilt uploading
BUG=chromium-os:4843,chromium-os:5855
TEST=./prebuilt_unittest.py
{'/b/cbuild/build/chroot/build/x86-dogfood/packages/x11-misc/util-macros-1.5.0.tbz2':
'gs://chromeos-prebuilt/host/version/packages/x11-misc/util-macros-1.5.0.tbz2',
'/b/cbuild/build/chroot/build/x86-dogf}
.FILTERING /usr/local/package/oob
FILTERING /var/tmp/bibby.file
.....Updating stage 20100309/stage3-amd64-20100309.tar.bz2 to stage
test_update
.
----------------------------------------------------------------------
Ran 7 tests in 0.002s
OK
Review URL: http://codereview.chromium.org/3452032
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
