Change-Id: I6593336a52b7298bd358f3e55531b2e6a9e6dff1
BUG=chromium-os:11883
TEST=Tried deleting the symlink and deleting the line from bashrc and things got updated; ran again w/ no problems.
Review URL: http://codereview.chromium.org/6480005
BUG=n0ne
TEST=./build_image and see it fail and ask me a question, instead of death
Change-Id: I27f7ac71ce74ff711e8b152ee202121d518045cd
Review URL: http://codereview.chromium.org/6417001
The original intent of this code was to prevent mounting
of the OEM partition. However, chromeos_startup mounts
/mnt/stateful_partition/home to /home and this file gets
hidden. Given that we might mount the OEM partition always
soon, removing this code.
BUG=chromium-os:11661
TEST=build_packages, build_image, ran suite_Smoke
Change-Id: I7ef4dd5c78484664cbdeb4ffaff26e2fcf8d2507
Review URL: http://codereview.chromium.org/6458007
I was getting the error about passing along an empty string argument, and this will fix that.
Change-Id: Iffd05fe570f3a6092bbeee05abf8a1884decd644
BUG=N0ne
TEST=remote testing in progress (no VM testing)
Review URL: http://codereview.chromium.org/6465014
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
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=4fc5227
Review URL: http://codereview.chromium.org/5271010
Change-Id: I1118a840e8ecc0ae0620003ea79ee0fd4174a96b
BUG=chromium-os:11811
TEST=Boot the system, and run 'xset'. Also, run the BVT suite
TEST=Test mod_image_for_test.sh --factory_install to see that there are no error messages
Review URL: http://codereview.chromium.org/6451009
As documented by the developer workflow, this script need to be
called from outside the chroot. This adds a temporary reference to
the new location of chromeos-common.sh, unbreaking the factory
workflow, and giving us time to come up with a better solution.
TEST=run inside the chroot and outside the chroot
BUG=chromium-os:11769
Change-Id: Icb90211111629ed037bc40682a94200d949050e0
Review URL: http://codereview.chromium.org/6462007
TEST=chromite works in new location
BUG=chromium-os:11507
Change-Id: I8e5dee287dd0120f1cd01966953b79cf53a14790
Review URL: http://codereview.chromium.org/6371018
This hack is necessary for old chroots to ensure that we source a good
common.sh when the one inside the chroot is out of date. We'll be able
to get rid of this after everybody has updated their chroot to have a working
version of common.sh and/or we have deprecated running scripts from the
source directory.
Also fix logic for when common.sh is missing to exit properly.
BUG=chromium-os:11598
TEST=Verify that build_image still works when the old common.sh is present in
the chroot.
Change-Id: I2e8c2fd5ad06446e669ad665ee2e70f4364958fe
Review URL: http://codereview.chromium.org/6286084
BUG=11507
TEST=Ran run_remote_test.sh and verified that the following is printed:
INFO : Detected cros_workon autotests. Building and running your autotests from /home/msb/trunk/src/third_party/autotest/files. To use emerged autotest, pass --use_emerged.
Change-Id: Ifc4305088e4edd059fad250d074347bc81a451cf
Review URL: http://codereview.chromium.org/6246141
Change-Id: Ia5e0042250da22cebadfd48d143f21597bcada5d
BUG=chromium-os:11716
TEST=Ran vm test and vm update scripts.
Review URL: http://codereview.chromium.org/6413019
Change-Id: I5f76f0f27b5789d88740b36fa6ce696ef7e68e8a
BUG=chromium-os:11602
TEST=Tried steps in bug 11602 (but hacked a sudo -K to the start of teardown_env so I didn't need to wait 15 mins).
Review URL: http://codereview.chromium.org/6286069
This is step 3/3, after cros_overlay_list is added to dev, and
after the ebuilds are updated to install from dev and not
crosutils, then this can go in.
Change-Id: I8ae26938fb14ccf6737acd9ca99b58aaf65a1aca
BUG=chromium-os:11507
TEST=None
Review URL: http://codereview.chromium.org/6392034
Change-Id: Ibd32a4be12e88d183dd0acbcb156582ad946c92f
BUG=chromium-os:11602
TEST=Added a 'sudo -K' as the first line of teardown_env to simulate sudo timeout, then performed steps in bug report (without 15 minute wait).
Review URL: http://codereview.chromium.org/6250116
Change-Id: I7eb27ac81704de8689a65203a440303a52a01dc2
BUG=chromium-os:11171
TEST=we'll see if things explode
Review URL: http://codereview.chromium.org/6286040
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
It's very rarely needed anyway but enter_chroot does everything under the sun.
Avoids:
error: could not lock config file ~/.gitconfig
Change-Id: Ide72b14fd434b182a88d2fc636559b3515905509
BUG=chromium-os:11523
TEST=Ran it ... 10x
Review URL: http://codereview.chromium.org/6312069
Fixes the following issue:
/home/msb/trunk/src/overlays/overlay-x86-generic/make.conf: line 7: prebuilt.conf: No such file or directory
BUG=11513
TEST=Verified that the error goes away.
Change-Id: I5b1dfab55394ba40c02e2a1a2ee7b03a5c4a7941
Review URL: http://codereview.chromium.org/6409031
cros_workon is the only user of cros_workon_common.sh
This is pre-requisite to moving cros_workon into devutils.git
BUG=11507
TEST=Ran ./cros_workon --board x86-generic --all list
Change-Id: I1eab551ab33646360e507328932c151a0d36f50a
Review URL: http://codereview.chromium.org/6347052
This issue seems bigger than it first appears because we had put extra logic to "Delete" the branch if we didn't rev anything. This CL basically takes out all the Deletes and relies and cros_mark_as_stable clean to clean up any old dirs correctly. To do this, I had to fix a bug in clean so that we actually delete the stable branch as part of it (if it exists).
EOM
Change-Id: Ic1020451dc1d492d4b6e2a233d1d49cf8c1c16b3
BUG=chromium-os:11329
TEST=Ran x86-generic-pfq w/ dev options + --chrome_rev=latest_release ...built chrome,
and revved packages without error. Doing more testing still.
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=a8ac0ec
Review URL: http://codereview.chromium.org/6291013
This reverts the commit a8ac0ec8c3.
TBR the x86 PFQ buildbot fails
BUG=chromium-os:11447
TEST=
TBR=sosa
Change-Id: I019de669db13b753365e1208acc9923c4bb5c993
Review URL: http://codereview.chromium.org/6339018
This issue seems bigger than it first appears because we had put extra logic to "Delete" the branch if we didn't rev anything. This CL basically takes out all the Deletes and relies and cros_mark_as_stable clean to clean up any old dirs correctly. To do this, I had to fix a bug in clean so that we actually delete the stable branch as part of it (if it exists).
EOM
Change-Id: Ic1020451dc1d492d4b6e2a233d1d49cf8c1c16b3
BUG=chromium-os:11329
TEST=Ran x86-generic-pfq w/ dev options + --chrome_rev=latest_release ...built chrome,
and revved packages without error. Doing more testing still.
Review URL: http://codereview.chromium.org/6291013
Change-Id: I24b498fffb7e7ce54517945730c91fecd1d57586
BUG=chromium-os:10723
TEST=Ran it and killed a test
Review URL: http://codereview.chromium.org/6260023
Change-Id: If4c2852568454c2dccf09b0fc1e180ed228a1bb7
BUG=chromium-os:4230
TEST=run cros_overlay_list from both locations in the chroot and src/scripts outside the chroot.
Review URL: http://codereview.chromium.org/6293021
Change-Id: Ie1ee6554ec0973a85a11c264346295fd27f59ebf
BUG=chromium-os:11329
TEST=Ran with cbuildbot on local system.
Review URL: http://codereview.chromium.org/6384017
It also caches sudo credentials before running jobs (for devs) and
exits if any updater returns an error code != 0 with the output
of pregenerate update
BUG=chromium-os:10723
TEST=Ran it ... killed one pregeneration to make sure it did print + exit
correctly
Review URL: http://codereview.chromium.org/6381013
Change-Id: I04842211e469b3a0022cb53b78efd17fbebe7010
If we are inside the chroot then we assume that the "gclient" root
is ~/trunk. If we are outside the chroot we continue with the
previous search mechanism to find the "gclient" root.
Change-Id: Ia40de609ea596228fec2644ff3046e376b112b06
BUG=chromium-os:4230
TEST=run "src/scripts/cros_overlay_list --board tegra2 --variant seaboard" inside and outside the chroot, and under sudo.
Review URL: http://codereview.chromium.org/6265028
Review URL: http://codereview.chromium.org/6344016
Not printing on the uart makes a huge difference in boot time performance. Since it's easy to re-enable again for those debugging boot time issues, let's disable it by default. It's how x86 does it as well.
Change-Id: Idb4af8d98434e70ee1389b3579c220da34be9c3b
BUG=chromium-os:11351
TEST=Build image and boot system
Review URL: http://codereview.chromium.org/6290011
Change-Id: I5dc22223559d3cdad357530af66c14115da63c89
BUG=n0ne
TEST=update_kernel to seaboard (and mario for regression test)
Review URL: http://codereview.chromium.org/6031005
