Change-Id: I5366fb930ca76f596f49d0312228aa5beeccbc31
BUG=chromium-os:8693
TEST=Ran it with and without dryrun and chrome uprev.
Review URL: http://codereview.chromium.org/5846005
Change-Id: I42a6110d41e79bb0ad50817e2e76b06f7973f6c2
BUG=chromium-os:10434
TEST=Ran it with --test_prefix for delay payload test and it succeeded.
Review URL: http://codereview.chromium.org/5877007
BUG=10425
TEST=Tested before and after.
Change-Id: Ic3e66805945f379a79562338b16845bb5dbd674f
Before: Machine hangs till power-cycle.
After: Machine reboots and we get a crash dump.
Review URL: http://codereview.chromium.org/5893005
Examples of how people might be using enter_chroot:
1. ./enter_chroot [chroot_flags] VAR1=val1 VAR2=val2 -- cmd arg1 arg2
Set env vars and run cmd w/ args
2. ./enter_chroot [chroot_flags] VAR1=val1 VAR2=val2
Set env vars and run shell
3. ./enter_chroot [chroot_flags] -- cmd arg1 arg2
Run cmd w/ args
4. ./enter_chroot [chroot_flags] VAR1=val1 VAR2=val2 cmd arg1 arg2
Like #1 _if_ args aren't flags (if they are, enter_chroot will claim them)
5. ./enter_chroot [chroot_flags] cmd arg1 arg2
Like #3 _if_ args aren't flags (if they are, enter_chroot will claim them)
I also updated the help to indicate that whole-command quoting is no longer
supported. If you really need whole-command quoting (maybe you want in-
chroot redirection), you'll need to use sh -c like:
./enter_chroot.sh -- sh -c "echo \"Save me\" > /tmp/save.txt"
You should avoid single quotes in the command and arguments. This isn't
a new limitation: it's shflags related.
Change-Id: I0452a8730ac9b8197834edc753b9eece69896135
BUG=chromium-os:7072
TEST=Tried a whole bunch of these commands.
Review URL: http://codereview.chromium.org/5840003
Also add some more information output when we detect that there
is nothing to do.
Change-Id: Ia3dcf0d3c276e10d3368d6bd508f3a0d72be79cd
BUG=chromium-os:8693
TEST=Ran it with all 3 paramaters and current overlay.
Review URL: http://codereview.chromium.org/5884004
We also print to /dev/stderr directly to avoid flushing issues which have been occassionally given us broken manifests printed out
Change-Id: I97819bbc31142432aa5ef926f99f2c4f90fd50ef
BUG=chromium-os:9714
TEST=Ran cbuildbot through sync
Review URL: http://codereview.chromium.org/5888003
Change-Id: I2760e33e1473ce04f7adeda39d0db5725eaa81ae
BUG=chromium-os:7072
TEST=Replaced ./build_packages with bash and ran command; valided env var set right.
Review URL: http://codereview.chromium.org/5930002
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
This change is in preparation for the new sudo, which corrects how
parameters are passed to subcommands.
Change-Id: I34d09d2716fbef137d02748a2934459a8a10d693
BUG=chromium-os:7072
TEST=Ran modified "update_kernel.sh" w/ old sudo and new sudo.
Review URL: http://codereview.chromium.org/5859002
Change-Id: I32c17e7353b420d7a895acffab4579c9b861095c
BUG=chromium-os:8693
TEST=Ran it with chrome_rev=tot, latest_release and stable_release
Review URL: http://codereview.chromium.org/5854001
This specifically gets the pfq one step closer to being completely ready to rev. We add --noprebuilts for the chrome pfq as its not ready to host prebuilts and instead we push unstable ebuilds. Anush noticed an Anush today where we are revving even when we don't change, and I've addressed this also in this CL.
Specifically:
1) Sort in cbuildbot long options by long format
2) Add --noprebuilts so that the Chrome PFQ can use this for now.
3) Fixed a unittest that had broken in a previous CL for cros_mark_chrome_as_stable.
4) Add ability for chrome to only rev if something really has changed:
-- This means, if the new ebuild either:
-- doesn't have the exact same chrome_version
-- or diff -Bu (actual diff) between last ebuild and new ebuild isn't the same (i.e. detecting a 9999 change or different CROS_SVN_COMMIT)
Change-Id: I9b289c2168d6868299573f5d7c7a676380ee497e
BUG=chromium-os:8693
TEST=Ran unittests (cbuildbot, cros_mark_*) and ran cbuildbot with new chrome pfq items.
Review URL: http://codereview.chromium.org/5783001
Change-Id: I1ac3ed12df00424ba5ba2d1c61fd6fe9716e13b9
BUG=chromium-os:9714
TEST=Ran new unittests as well as ran cbuildbot on local b/cbuild
Review URL: http://codereview.chromium.org/5689003
Change-Id: Ib9fcc078d8e0223cd1b1376db91d8e71ae8359a6
BUG=cp file to itself fails in case of nostatefuldev
TEST=ran build_image with and without statefuldev
Review URL: http://codereview.chromium.org/4959001
Patch from Trevor Bourget <tbourget@codeaurora.org>.
Change-Id: Id4ed6af96e0b621f4ad36966fad45c887b991373
BUG=None
TEST=Ran a fresh build_packages and build_image for x86-generic.
Review URL: http://codereview.chromium.org/5689004
On ARM platform read kernel from device passed in from u-boot
instead of hardcoding it to 0
BUG=none
TEST=emerged on seaboard, booted from SD card and emmc
Change-Id: Ia4506ed9f85d94eb37a9ac57430e1490d106c403
Review URL: http://codereview.chromium.org/5612008
Patch from Allen Martin <amartin@nvidia.com>.
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
Use general purpose wait in case your connecting to a vm
that you didn't start.
Change-Id: Ie67e2d3235882d372d04e4a44d0781ddfc8d4645
BUG=chromium-os:10121
TEST=Ran it, caused some crashes. Still ran test after retries.
Review URL: http://codereview.chromium.org/5757001
This allows us to avoid deleting the board and still ensure our packages are
in sync with the full buildbot. This allows us to detect conflicts between
old and new packages.
BUG=chromium-os:10127
TEST=Run cbuildbot.py with emptytree feature forced to on and verify that
build_packages rebuilds all packages. Also run unit tests.
Change-Id: I83e186937e28eef44285724697895a4583910b58
Review URL: http://codereview.chromium.org/5652007
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
archive_build.sh has code to archive host prebuilts, but the code isn't working because of a typo in archive_build.sh.
The typo: $FLAGS_board is misspelled as $FLAGS_BOARD.
BUG=chromium-os:10148
TEST=Ran prebuilt.py with --sync-host option
Change-Id: I50129b1fdfb931b1c076a064b970d7d943f556ac
Review URL: http://codereview.chromium.org/5724001
into mod_image_for_test.sh rather than slightly different versions
of the same in image_to_usb.sh and image_to_vm.sh
Added a function to get a test image into common.sh
Added --inplace option to mod_image_for_test, which is the default,
and preserves the original behaviour. But using --noinplace it will
now do the copy for you.
Found that chromiumos_image.bin appears throughout the scripts, so added it and the test variant to common.sh
BUG=chromiumos-10126
TEST=run mod_image_for_test.sh with and without --noinplace
run image_to_usb.sh and image_to_vm.sh with both options
test on Seaboard that correct image is provided
Really we should have automated testing for these scripts
Change-Id: I5cfa91792c7fded35e7f4ca8f8f27c6b270817fb
Review URL: http://codereview.chromium.org/5271010
Change-Id: I0dda2cfb6e11cb69a6a1a6a4bae478cab78b8947
BUG=chromium-os:8693
TEST=Ran it with cros_mark_chrome with stable_release
TBR=Config change to get chrome builder up.
Change-Id: I1d0e546f6ea837928ba426e4690007ef2649f68e
BUG=10102
TEST=test KVM with -net virtio and ensure it boots and can copy files in etc
Review URL: http://codereview.chromium.org/5543006
This server requires that unsafe characters are quoted in URLs, so we do that
here.
Change-Id: I6b7c430671b02a8da11777029b0fdb59a87dcae1
BUG=chromium-os:9902
TEST=Ran unit tests. Ran example buildbot run and diff'd new version and old
version of Packages file.
Review URL: http://codereview.chromium.org/5542002
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
Chrome PFQ right now is uploading prebuilts which wasn't meant to happen :(
Change-Id: I502a0621a6c9f655e5a3f890dd79e00652925902
BUG=chromium-os:8693
TEST=Ran cbuildbot with --debug
Review URL: http://codereview.chromium.org/5595004
Also, fixed to honour external FEATURES for the install case.
BUG=n0ne
TEST=Built a kernel with this CL.
Change-Id: I17d50cc382b297766761f12d47a555630fedc016
Review URL: http://codereview.chromium.org/5530004
Change-Id: Ia94f1c983aec533fc2813f9c300266d394b8ee7c
BUG=chromium-os:9946
TEST=Ran ctest and saw through the download and start of the test harness
Review URL: http://codereview.chromium.org/5628002
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
We also fix some of the configs for existing configurations.
Change-Id: I34baa9664ff9e91268c8bac976ab2ab0aee51bfb
BUG=chromium-os:9714
TEST=Running now with cbuildbot x86-generic-pre-flight-queue.
Review URL: http://codereview.chromium.org/5531002
