Change-Id: I407d39ca461bbe609812e2b3bd2a51e67e331659
TEST=manually built a recovery image (non-dev mode, --withnodev) and verified
chromeos-install completed successfully when installing from USB to target HD
Review URL: http://codereview.chromium.org/3174005
Takes effect when you sync/re-enter chroot.
Also, minor non-exhaustive style cleanup of existing code.
BUG=5623
TEST=tried tab completion with ./cros_workon and various options
Change-Id: I46d2eb29205a3a4ce350b82e7eced7f2069095ca
Review URL: http://codereview.chromium.org/3185003
When we pass on --jobs to individual emerge processes, it causes them
to hide their output. This makes it harder to debug why they are
failing or hanging. Example: http://goo.gl/C6Ru
TEST=Made sure that output is shown by emerge processes when --jobs is used.
BUG=chromium-os:5684
Review URL: http://codereview.chromium.org/3168012
The ltp tests don't pass, and take a long time to build. Once they pass,
it'll make sense to add them back. But otherwise, no point waiting for their
long build process to complete.
BUG=none
TEST=Run build_packages --withautotest
Review URL: http://codereview.chromium.org/3121010
This should cut several minutes off the time for build_packages --nousepkg
--showoutput.
TEST=Ran build_packages --showoutput, verified output.
BUG=chromium-os:5647
Review URL: http://codereview.chromium.org/3106008
TEST=Ran cros_mark_all_as_stable with packages and without packages to
mark and had them both succeed with exit code 0.
BUG=5486
Review URL: http://codereview.chromium.org/3179004
Autotest installs stuff to the image via ssh, so there's no need to include
all of this stuff to the image. This saves disk space. Note that
/usr/local/autotest-chrome is currently already excluded from the image
because of a hack in the chrome ebuild, and that /usr/local/autotest is
usually also excluded from the image because autotest is not included
as a dependency of any packages that are installed.
In the factory setting, it looks like the factory has its own code for
installing autotests via rsync. Presumbably, if the factory tests are
managing the autotest directly, they won't want emerge mucking with the
directory as well on the image. Currently, emerge doesn't muck with the same
directory, but we probably want to ensure that it doesn't start doing that in
future to ensure sanity.
TEST=Built images. Modded for factory test. Verified that (a) build directory contains autotests, (b) regular images do not contain autotests; and (c) images modified for factory test do contain autotests
Review URL: http://codereview.chromium.org/3124010
Ugh, it worked on my machine because of my .ssh/config but need to
explicitly specify port for it to work on buildbot.
TBR=sosa
BUG=5532
TEST=This change was in the previous location of cbuilbot.py and working
correctly.
Change-Id: Id53a76bcb5d43c37ac725267864048d833f5a6ee
Review URL: http://codereview.chromium.org/3144005
By default, emerge will pause and beep when it has messages that it wants the
user to see. This beeping is not useful during a parallel merge, so we turn it
off.
TEST=Ran parallel_emerge udev. It stopped beeping and completed faster.
BUG=none
Review URL: http://codereview.chromium.org/3080005
TEST=Ran locally outside of chroot. Required change to remove Exception OSError as
e because "as" is a Python 2.6'ism
Review URL: http://codereview.chromium.org/3146001
* Only run the regenerate once, after start
* Make regenerate preserve old projects from local manifest
* Make pkgname not found a non-fatal error
* Delete misc debug messages
modified: cros_workon
Review URL: http://codereview.chromium.org/3115001
This script wraps the old memento udpate generator and the new delta
updater. It will also generate new-style full updates soon, which are
full updates that use the delta-update format, when that code is ready.
BUG=5248
TEST=ran local script to do full/delta update
Review URL: http://codereview.chromium.org/2873082
BUG=5130
TEST=create a test image, boot it on a device, and run "sudo nsscertutil -d "sql:/etc/fake_root_ca/nssdb" -L -n FakeCert | less". Look at the section of the output marked "Validity:" and make sure the Not Before and Not After sections indicate dates that are 3 weeks apart
Change-Id: I67cf7e71027147f83c1bc916557bc06ef66fa0e0
Review URL: http://codereview.chromium.org/3075025
BUG=none
TEST=run build_image, happen to finish on a time with less than 10 seconds in it, watch the missing 0-padding
Review URL: http://codereview.chromium.org/3050047
BUG=none
TEST=run build_packages on --board=tegra2_dev-board-opengl right now, since binhost hasn't been populated yet.
Review URL: http://codereview.chromium.org/3035058
Copying the .ssh directories within client takes up O(2n) space in
the stateful partition
BUG=none
TEST=reran mod_image_for_test.sh
Review URL: http://codereview.chromium.org/2832079
Also update parallel_emerge to print output in general if you hit
CTRL-C or if a job is running for more than an hour. Also cleanup exit
handling so that emerge exits a bit more cleanly, and so that we don't
hang if emerge throws an Exception.
BUG=none
TEST=Ran ./parallel_emerge --show-output -uDNve chromeos
Review URL: http://codereview.chromium.org/3010056
* This allows to block a list of ebuilds from being uprevved by the PFB
* With little modification, there could be a GUI which allows people to manage
a blacklist on the server, with stating the reason
(ex.: autotest-tests - $me, creating the ebuild, unstable for now)
modified: cros_mark_all_as_stable
TEST=
1) create a blacklist:
chromeos-base/autotest
chromeos-base/autotest-tests
2) run ./cros_mark_all_as_stable --board=x86-generic
...
INFO : chromeos-base/autotest blacklisted, skipping
INFO : chromeos-base/autotest-tests blacklisted, skipping
...
Review URL: http://codereview.chromium.org/3076038
* Also changes the way how "new workflow" is detected in run_remote_tests.sh
modified: autotest_run.sh
modified: run_remote_tests.sh
Review URL: http://codereview.chromium.org/3048051
Using git-cl push requires setting up Rietveld authentication
cookies on the bots. This is non-trivial. So instead just use
git. This removes a point of failure.
BUG=5258
TEST=Verified by successfully pushing.
Change-Id: Ic3cd68f2d2a9cc59bbe69270896172ee4a418226
Review URL: http://codereview.chromium.org/3015061
Change-Id: I7d17db3cb522a52ec2dac688f4bf83fb5ae6a2d1
related CL: http://codereview.chromium.org/3031049/show
TEST=(1)Manually built an image using build_image script, which exercised "build_gpt.sh"; (2) manually built a Qemu VM image using "image_to_vm.sh" and verified the VM is bootable (up to login screen); (3) manually built a dev recovery image using "mod_image_for_dev_recovery.sh" and verified image functions properly for dev recovery purpose
Review URL: http://codereview.chromium.org/3050039
Change-Id: I43f88cbe4df74e254299a95c5e1b62a300230385
Undo part of commit by drewry
http://chromiumos-git/?p=crosutils.git;a=commit;h=7ab698d713bcad066f0ee0469fbbcaa274411d08
mod_image_for_dev_recovery.sh modifies a dev install shim image (already
bootable) by altering content of its stateful partition. The result image does
NOT need to be made bootable again.
TEST=manually built a dev recovery image (based on a factory install shim) and
verified recovery functionality on agz device with cros fw
Review URL: http://codereview.chromium.org/3074037
Adds arm_extra_bootargs to boot.desc and to cros_make_image_bootable.
TEST=tegra2 dev-board build_packages, build_image --fast worked
BUG=broken tree
Change-Id: Ifdfeda66f1eb5e5b1e618706eeba269f31fa9913
Review URL: http://codereview.chromium.org/3069031
Breaks make_image_bootable out of build_image into a separate
script. In addition, it make a helper .sh in the OUTPUT_DIR
to let make_image_bootable be re-run on an image with the same
arguments that were passed in via build_image.
This change also removes the use of the boot/ directory in
OUTPUT_DIR.
TEST=build_image verified; image_to_usb --test_image; booted l13
build_image; image_to_vm; qemu booted
build_image verified; image_to_usb; booted l13
BUG=chromium-os:5081
Review URL: http://codereview.chromium.org/3066037
Change-Id: I627d678089aa71c353347f387ad5b14063fd4e7b
BUG=none
TEST=use this script with a (correct) password that includes punctuation such as one of these: $&+,/:;=?@
Review URL: http://codereview.chromium.org/3058046
Instead of using master, use the tracking branch.
BUG=5258
TEST=Verified that cleanup now works with repo.
Change-Id: I6e415d9068d54b602238b89c77ba4dbe2f9ff4c6
Review URL: http://codereview.chromium.org/3076035
This is a temporary hack to allow cros_mark_as_stable to work outside
the chroot. Eventually, we'll re-write the code to use optparse.
BUG=5412
TEST=Verified the cros_mark_as_stable now works outside the chroot.
Change-Id: Ife1f7aeadb70ba004d3928a9c71d6e95c042833d
Review URL: http://codereview.chromium.org/3037046
The tracking branch is different between repo and gclient.
BUG=5258
TEST=Verifed the tracking branching option is correctly propagated.
Change-Id: I9e5b8cb68d335c47e47499b4964dcaa83ac26f76
Review URL: http://codereview.chromium.org/3037045
All Qual DBs may be existed in the same directory of hardware_Components (overlaid internal git). So, if QUALDB is not specified, first check the existence of DBs matched the board name. Then remove other DBs not belonging to the board.
TEST=build_packages, build_image, image_to_usb
Review URL: http://codereview.chromium.org/3032036
build_image creates it after a successful build, and get_latest_image
can use it if it exists. Fall back to old behavior for now when there
are directories without a link.
BUG=none
TEST=Try building an image, check link. Rebuild, check new link.
Review URL: http://codereview.chromium.org/3014051
Currently, our build occasionally fails with errors about about symlinks
already existing. This usually only slows down the build, because we have
retries, but it would be good to fix the problem.
This patch updates parallel_emerge to use the no-env-update feature for cross-
compiles. This feature skips the env_update step, which isn't thread-safe, and
isn't necessary for when we're cross-compiling and don't actually need to run
the binaries. Instead we run the env_update at the end, avoiding a thread-safety
issue.
TEST=Ran full build --nousepkg with env_update occuring at end.
BUG=chromium-os:5382
Review URL: http://codereview.chromium.org/3034051
When --onlydeps is specified, we don't want to merge packages that were
specified on the command-line. Previously, it threw an exception in this
case because it couldn't find the command-line packages in the list of
installed packages.
TEST=Run ./parallel_emerge --onlydeps autotest, and make sure it
doesn't crash.
Run ./parallel_emerge --board=x86-generic -po chromeos power_manager and make sure it does emerge power_manager, and doesn't crash.
BUG=none
Review URL: http://codereview.chromium.org/2868094
