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
Modifying gsdcurl to accept username and password from the environment. Switching cros_download_latest_image to use gsdcurl
Merge branch 'master' of ssh://chromiumos-git/crosutils
Switching back to MixedCase. Wrong style guide...
Switching to match external style guide.
Dropping unneeded arg as per review.
Fixing copyright.
Making the prompts go to stderr. Renaming for tab completion.
Adding gsdcurl utility for pulling for Google Storage for Developers.
BUG=None
TEST=None
Review URL: http://codereview.chromium.org/3060043
This conforms to the new layout of scripts in which all scripts
other than make_chroot and enter_chroot are installed in the
chroot using an ebuild.
Review URL: http://codereview.chromium.org/3084012
This change checks for and sources shflags from /usr/lib before
depending on the gclient-style path.
TEST=None
BUG=4230
Review URL: http://codereview.chromium.org/3010045
Change-Id: I3085c2356c40c691a2a72bf79c1d9167162d6dca
The icedtea and o3d packages take a really long time to rebuild (over 30 mins
each), so we can give our developers a break if we exempt them from automatic
rebuilds.
TEST=Rev the portage ebuild or the fontconfig ebuild and run build_packages.
Without the change, takes over 45 mins. With the change, it takes 5 mins.
BUG=none
Review URL: http://codereview.chromium.org/3029051
Rather than using split, we can just use os.path.basename(path) to get
the username from the homedir name. This is a bit simpler.
I've also added a comment which I missed in my last commit.
TEST=Ran ./parallel_emerge, verified the new method of getting
PORTAGE_USERNAME gets the right username.
BUG=none
Review URL: http://codereview.chromium.org/3056002
This script generates the list of overlays, including variant
overlays, for a particular board/variant combination. It will
be called from setup_board.
Review URL: http://codereview.chromium.org/3080019
This is required to enable running cros_mark_as_stable from outside
the chroot.
BUG=5258
TEST=Successfully ran outside the chroot and pushed a change.
All unit tests continue to pass.
Change-Id: Ibd23ace6326b8453c132c416d6db6e42c8c2c239
Review URL: http://codereview.chromium.org/2884060
Code was changed to add a CR. Fix tests to accomodate.
BUG=5258
TEST=Unittests pass again.
Change-Id: Iacdbffb14d14f60a43883db3ee12b99a5eeb9f65
Review URL: http://codereview.chromium.org/3014045
Currently, cros_mark_as_stable.py does not add a newline after its
CROS_WORKON_COMMIT="" line. This works fine for 9999 ebuilds that have a newline
after the EAPI="" line, but doesn't work for ebuilds that don't do this.
This should fix the preflight queue build.
TEST=Ran cros_mark_as_stable.py on the update engine and verified that the
CROS_WORKON_COMMIT="" line was not joined together with the next line.
BUG=none
Review URL: http://codereview.chromium.org/3036029
I tried to disable parallel_emerge yesterday, but my change didn't work,
so the buildbots are still running into occasional related issues.
Portage has two flags for doing collision protection: collision-protect
and protect-owned. The protect-owned feature is enabled by default and
is quite useful: it checks to make sure that we don't have multiple
packages that own the same file. The collision-protect feature is more
strict, and less useful: it fails if it finds a conflicting file, even
if that file was created by an earlier ebuild that failed to install.
We want to disable collision-protect here because we don't handle
failures during the merge step very well -- we just leave the old
Unfortunately, we haven't quite figure out the best way to handle
these failures in parallel emerge, so for now we disable the flag.
TEST=Created a fake collision, made sure that packages still merge.
BUG=none
Review URL: http://codereview.chromium.org/2825076
* Let's face it: I broke it in the last second when i renamed the function but not
the place where it's being called, and now cros_workon is dead.
modified: lib/cros_workon_common.sh
Review URL: http://codereview.chromium.org/3052025
This will allow replacement of equery which in cros-workon
Also other ebuild-related operations like grouping workon ebuilds with the same repo
* Find for all ebuilds takes almost no time when cached and up to ~2 secs when not
* equery takes ages just to load
TEST=cros_workon_ebuilds before and after, and diff:
--- list1 2010-07-27 21:22:23.000000000 -0700
+++ list2 2010-07-27 21:22:32.000000000 -0700
@@ -1,6 +1,5 @@
app-crypt/tpm-emulator
app-crypt/trousers
-app-i18n/ibus
app-i18n/ibus-chewing
app-i18n/ibus-hangul
app-i18n/ibus-m17n
(ibus is a mistake, not a workon package, i'll fix that in a separate CL)
modified: lib/cros_workon_common.sh
Review URL: http://codereview.chromium.org/2808072
collision-protect doesn't make sense for parallel_emerge, because
we don't lock around merges. Also, if merge fails part-way through,
it's strange to fail just because some files are lying around.
This fixes an issue with the buildbots.
TEST=Checked that collision-protect feature gets deleted by this.
BUG=none
Review URL: http://codereview.chromium.org/3061029
The fast build is stable enough now that we can enable it for everybody.
I ran the build constantly all weekend on two machines and I only ran into
one (rare) error, which I've fixed in a separate patch.
See <http://codereview.chromium.org/2856048/show>
TEST=Ran lots and lots of fast builds
BUG=none
Review URL: http://codereview.chromium.org/3059001
BUG=chromium-os:1888
TEST=Manual. build_image should run fine when oem_customization flag is not specified.
Review URL: http://codereview.chromium.org/3076009
BUG=4828
TEST=make sure factory image actually builds while chrome ui autotests are included in the build
Review URL: http://codereview.chromium.org/3010035
The DBs are named in the format of qualified_components_${BOARD}_${HWQUALID}.
If only one hwqual id for the board, named in qualified_components_${BOARD}.
Review URL: http://codereview.chromium.org/3038026
* This script should replace the call to ebuild in autotest wrapper, and essentially
duplicates all the test running functions from autotest-0.0.1.ebuild
* duplicate autotest wrapper into autotest_workon to separate conversion and old functionality
* Add a hack into run_remote_tests to allow using autotest_workon instead
new file: autotest_run.sh
new file: autotest_workon
modified: run_remote_tests.sh
Review URL: http://codereview.chromium.org/2854062
The last changes to the installer broke image_to_vm. Since image_to_vm
doesn't need to run postinst, but just change the active image, it
now just calls chromeos-setimage and passes in its needed flags (already
supported by the last installer change). It will also detect whether
the image was built with verification of the rootfs enabled or not
by looking at the default.cfg file.
Also updates the location of where you should run the command in
build_image.
TEST=built a new image with --enable_rootfs_verification and started with qemu -curses -hda [output]; did the same without verification
BUG=chromium-os:2963
Review URL: http://codereview.chromium.org/3034030
Change-Id: I265d6ad8971f9427b78cc07d784fced9cceb5974
With the newest Chrome OS BIOS and bootstub, this will be expanded to the
booted kernel partition's UniqueGuid, so that the kernel device can be
determined with certainty, since the BIOS and kernel may enumerate drives
differently.
You can identify the booted kernel partition at runtime with something like
this:
sudo cgpt find -1 -u \
$(cat /proc/cmdline | sed 's/.*kern_guid=\([0-9a-f-]\+\).*/\1/')
Review URL: http://codereview.chromium.org/3035020
TEST=Ran using default option and then tried -t chromiumorg/master and
saw a correct failure since I don't have that branch to track against.
Review URL: http://codereview.chromium.org/3032019
