The only reason we have bash in the cros overlay is so that we have it
not install a /bin/sh symlink pointing to bash in the board root. Once
we move that handling to chromeos-base, we can drop all the bash ebuild
customizations.
BUG=chromium-os:21901
TEST=`emerge chromeos-base bash` and see /bin/sh -> bash
TEST=`emerge-amd64-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-arm-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-x86-generic chromeos-base dash` and see /bin/sh -> dash
Change-Id: I1df4a75ac314ed308817b4cdf61564ac0174ad63
Reviewed-on: https://gerrit.chromium.org/gerrit/11409
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
The only reason we have dash in the cros overlay is so that we can install
a /bin/sh symlink pointing to dash in the board root. Once we move that
symlink to chromeos-base, we can drop all the dash customizations.
BUG=chromium-os:21901
TEST=`emerge chromeos-base bash` and see /bin/sh -> bash
TEST=`emerge-amd64-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-arm-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-x86-generic chromeos-base dash` and see /bin/sh -> dash
Change-Id: Iaec86219ad64d086e261187e6f7c3436eb7890cd
Reviewed-on: https://gerrit.chromium.org/gerrit/11408
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The newer ncurses includes fun pkg-config files which other packages
can now use instead of the crappy ncurses5-config scripts.
For example, newer gpsd ebuilds will utilize these .pc files.
BUG=chromium-os:467
TEST=`emerge ncurses` works
TEST=`emerge-amd64-generic ncurses` works
TEST=`emerge-arm-generic ncurses` works
TEST=`emerge-x86-generic ncurses` works
TEST=build_packages+build_image for x86-alex boots up
Change-Id: Ib084c0e219be14622b5e38c6c2ae552368273bb5
Reviewed-on: https://gerrit.chromium.org/gerrit/12393
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Some core eclasses were updated recently (notably eutils), so regenerate
the cache manually to take that into account.
BUG=None
TEST=build_packages works for x86-alex
Change-Id: Ia06d9697d29b185d2bb859049dba73df3010276f
Reviewed-on: https://gerrit.chromium.org/gerrit/12390
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This reverts commit 84b6463197a21a16cf1f3ce70cafaed32a979057.
BUG=chromium-os:21244
TEST=build grub and see new grub installed (after related unmasking in chromiumos-overlay)
Change-Id: I57f1a63baee9667cb4907975abef736c1dfb4622
Reviewed-on: https://gerrit.chromium.org/gerrit/12255
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Anush Elangovan <anush@chromium.org>
Commit-Ready: Anush Elangovan <anush@chromium.org>
I got antsy and merged gtest into the portage-stable repo before I
should have, so now upgrading gmock/glog fails because the config
wrapper from gtest doesn't get wrapped with existing installs.
(See commit 2cfb1bfb4742e917d4d7e629 in the chromiumos overlay).
Force everyone to upgrade so the hook fires and wraps the script.
BUG=chromium-os:21276
TEST=`emerge gtest gmock glog` still works
Change-Id: I9137b3e9367040fe6a078499ddedcfe41a34df69
Reviewed-on: https://gerrit.chromium.org/gerrit/12333
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The upstream Gentoo version of the glog ebuild should cover all our
existing needs.
BUG=chromium-os:21276
TEST=`emerge-arm-generic glog` works w/out -I/-L hacks
TEST=`emerge-x86-generic glog` still works
TEST=`emerge glog` still works
Change-Id: I4af4ab4f2e8319a97f9315d4b3dc6dff857fdeee
Reviewed-on: https://gerrit.chromium.org/gerrit/11579
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Chris Wolfe <cwolfe@chromium.org>
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The upstream Gentoo version of the gmock ebuild should cover all our
existing needs, but it also includes some build fixes which make cross
compiling work nicely (running elibtoolize).
BUG=chromium-os:21276
TEST=`emerge-arm-generic gmock` works w/out -I/-L hacks
TEST=`emerge-x86-generic gmock` still works
TEST=`emerge gmock` still works
Change-Id: I10176d5eff98b7dfb4e0294409969ad36f90715d
Reviewed-on: https://gerrit.chromium.org/gerrit/11578
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Chris Wolfe <cwolfe@chromium.org>
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Newer versions of util-linux's mount utility will not show:
/dev/loop0 on /some/path type ext3 (mount,opts)
Instead, it finds out the file backing /dev/loop0 and outputs:
/some/file on /some/path type ext3 (mount,opts)
This breaks the make_image_bootable helper that attempts to look up the
loop device that mount_gpt_image.sh happened to pick.
Let's scuttle the idea of parsing `mount` and move directly to what the
kernel has to say via /proc/mounts. Hopefully the ABI there should be
quite a bit more stable.
BUG=None
TEST=build_image works with mount from util-linux-2.16
TEST=build_image (before change) fails with mount from util-linux-2.19
TEST=build_image works with mount from util-linux-2.19
Change-Id: I66908800e82ff2e106face9d57773721e400dc2a
Reviewed-on: https://gerrit.chromium.org/gerrit/11869
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This is final step in ext4 conversion. We have been running with
the ext4 file system but ext3 format for several weeks. This changes
uses the ext4 format for the stateful partition.
Removed make_developer_script_runner.sh as per review.
BUG=chromium-os:20012
TEST=Ran ext4 on all platforms
Change-Id: I8e1564bfa576e9a0ad810879c18223a6c68b18e1
Reviewed-on: https://gerrit.chromium.org/gerrit/11220
Commit-Ready: Paul Taysom <taysom@google.com>
Reviewed-by: Paul Taysom <taysom@google.com>
Tested-by: Paul Taysom <taysom@google.com>
Upgraded net-dns/c-ares to version 1.7.5 on arm, x86.
This is step 1. Step 2 will be to enable 1.7.5 for arm, amd64, and x86,
in chromiumos-overlay/profiles/targets/chromeos/package.keywords.
BUG=chromium-os:22470
TEST=built x86-alex and arm-generic
Change-Id: I91c64972c8ac107cec75530e09ef977fc549db69
Reviewed-on: https://gerrit.chromium.org/gerrit/12315
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Jason Glasgow <jglasgow@chromium.org>
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Tested-by: Jason Glasgow <jglasgow@chromium.org>
We're seeing some HZ warnings on ARM platforms due to a bug in the
internal procps init sequence. This has already been fixed in the
upstream Gentoo ebuild, so pull down the latest stable from there.
BUG=chromium-os:20777
TEST=`emerge procps` works
TEST=`emerge-amd64-generic procps` works
TEST=`emerge-arm-generic procps` works
TEST=`emerge-x86-generic procps` works
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
Change-Id: If635416e7e28ede1b60cf8067aa4f77aabb4a4d8
Reviewed-on: https://gerrit.chromium.org/gerrit/12000
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Upstream Gentoo has split the user tools out into a dedicated eclass.
If we merge this back into our tree, we can then easily override all
of the user.eclass funcs so we can do our own management and not worry
about transient UID changes. But this is only useful if we also grab
the updated eutils.eclass which no longer overrides these funcs.
BUG=chromium-os:22128
TEST=`cbuildbot amd64-generic-full` worked
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
TEST=`cbuildbot chromiumos-sdk` worked
Change-Id: I404ff7dad38817648b827079f5a5839a83377df8
Reviewed-on: https://gerrit.chromium.org/gerrit/12207
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upstream Gentoo has split the user tools out into a dedicated eclass.
If we merge this back into our tree, we can then easily override all
of the user.eclass funcs so we can do our own management and not worry
about transient UID changes.
At the moment however, nothing is using this, so importing it should
not cause any problems.
BUG=chromium-os:22128
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
Change-Id: If756563e76ce91b07ccb54e036822073be7cee60
Reviewed-on: https://gerrit.chromium.org/gerrit/11993
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Now that gsutil is in upstream Gentoo, we can migrate to that from the
version in the chromiumos overlay.
BUG=chromium-os:23473
TEST=`gsutil cp gs://chromium-browser-continuous/index.html ~/` works
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
Change-Id: I44e7f513c307dd1f912fe6e27423cc1b23341665
Reviewed-on: https://gerrit.chromium.org/gerrit/12136
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upstream Gentoo has added dev-python/mox which is the same thing as our
local dev-python/pymox. So import the upstream Gentoo ebuild so we can
drop our local ebuild.
BUG=None
TEST=`emerge mox` works
TEST=cros_portage_upgrade_unittest passes
TEST=build_packages+build_image for x86-alex boots
TEST=buildbot's run_tests passes
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
Change-Id: I8efbb6a7e62e1ff0ffdecbc7da6f17dbd723e2ae
Reviewed-on: https://gerrit.chromium.org/gerrit/12145
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Newer python packages (boto/gsutil/etc...) need the newer eclass.
BUG=chromium-os:23473
TEST=`emerge boto` works
TEST=`emerge gsutil` works
TEST=`emerge protobuf` works
TEST=`emerge argparse` works
TEST=`emerge setuptools` works
TEST=`emerge pylint` works
TEST=`emerge pyopenssl` works
TEST=`emerge pyudev` works
TEST=`emerge pyusb` works
TEST=`emerge pyxdg` works
TEST=`emerge imaging` works
TEST=`emerge astng` works
TEST=`emerge pymox` works
TEST=`emerge gdata` works
TEST=`emerge logilab-common` works
TEST=`emerge m2crypto` works
TEST=`emerge cherrypy` works
TEST=`emerge pycairo` works
TEST=`emerge numpy` works
TEST=`emerge gentoolkit` works
TEST=`emerge scons` works
TEST=`emerge hdctools` works
TEST=`emerge file` works
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
Change-Id: I546e9fe9042baf4e6082364ee756d47f61be0763
Reviewed-on: https://gerrit.chromium.org/gerrit/12134
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Some newer ebuilds use syntax that is supported only in newer versionator
eclasses, so pull down the latest version.
The eclass should be backwards compatible with older ebuilds.
BUG=chromium-os:23473
TEST=build_packages+build_image for x86-alex boots up
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
Change-Id: I0e4f9c1edf2ffc20f6991245c83bb07ac79b0fa3
Reviewed-on: https://gerrit.chromium.org/gerrit/12133
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Upstream Gentoo has added a dedicated eclass for working with scons
projects. Nothing in the tree uses this yet, but some packages down
the line will.
BUG=None
TEST=None
Change-Id: Ibdfe1b7386e4cdbecc7c1cdc981092cda4993332
Reviewed-on: https://gerrit.chromium.org/gerrit/11994
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This syncs with the upstream Gentoo ebuild which has arm stable.
BUG=chromium-os:23473
TEST=`emerge-arm-generic scons` works
Change-Id: I1e8ed9a7a98d40df0b4afb3e61bcdcd00618c5a4
Reviewed-on: https://gerrit.chromium.org/gerrit/12002
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
We need this for the upstream gsutil package, but nothing locally uses
it right now.
BUG=chromium-os:23473
TEST=`gsutil cp gs://chromium-browser-continuous/index.html ~/` works
Change-Id: I951ff1d8d51e335d2563cf985a55f280bb921746
Reviewed-on: https://gerrit.chromium.org/gerrit/12135
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
It seems better to catch issues earlier during the build phase rather than later
during the actual test run. Prompted to do this after debugging
crosbug.com/21837.
BUG=chromium-os:23422
TEST=build_image test for x86-alex, amd64-generic, tegra2_kaen with no failures;
build_image factory_test for x86-alex with no failures; also verified that
build_image exits early with a non-zero exit code for amd64-generic without the
fix for crosbug.com/21837.
Change-Id: Ibdcf770d1d854d5a6765734556cf6ee8fc4aae96
Reviewed-on: https://gerrit.chromium.org/gerrit/12102
Tested-by: Darin Petkov <petkov@chromium.org>
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Ready: Darin Petkov <petkov@chromium.org>
Race conditions could prevent /tmp/esp.* from being properly unmounted
if it was quickly mounted then unmounted. If the umount fails,
sleep briefly and then retry.
BUG=chromium-os:23442,chromium-os:23443
TEST=Ran build_image --test, saw umount failure but after script finished
saw that directory was unmounted on second attempt so no leakage
Change-Id: I5b2260f5c99fcfa66027ebcfd69b6e3d5afe4b91
Reviewed-on: https://gerrit.chromium.org/gerrit/12115
Tested-by: Jon Kliegman <kliegs@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Jon Kliegman <kliegs@chromium.org>
/tmp/esp.* mountpoints are being leaked in update_bootloaders so clean
these up too.
BUG=chromium-os:23442
TEST=With stale mounts existing, run script. Observe mounts gone
Change-Id: I95729bd7330157d02f27f86da495642263fe8ff6
Reviewed-on: https://gerrit.chromium.org/gerrit/12114
Tested-by: Jon Kliegman <kliegs@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Jon Kliegman <kliegs@chromium.org>
See CL https://gerrit.chromium.org/gerrit/#change,11951 for the original CL.
BUG=chromium-os:23407
TEST=Tested on chroot synced on 23/11/11
Change-Id: I039d6b6ee06617dfa9263eab4fe83e128f0773b4
Reviewed-on: https://gerrit.chromium.org/gerrit/12106
Reviewed-by: Peter Mayo <petermayo@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Sean Paul <seanpaul@chromium.org>
Commit-Ready: Sean Paul <seanpaul@chromium.org>
This reverts commit c4412d9028298f65cf2768493a508ed9790702e7
Change-Id: I19f052d98e3029478f946cca1b52c1ae5f49204a
Reviewed-on: https://gerrit.chromium.org/gerrit/12068
Reviewed-by: Jon Kliegman <kliegs@chromium.org>
Tested-by: Sean Paul <seanpaul@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
The current instructions for golo access include additions to the
~/.ssh/config file that are specific to Google distros of ssh. The
filtering mechanism in enter_chroot needed an update to include
these new options to filter out.
BUG=chromium-os:23322
TEST=With a golo-configured .ssh/config, enter chroot and test ssh:
> cros_sdk
> git remote update
Fetching ...
...
Change-Id: Ida9fcdff37ff0eb24c811ad789f82136dca7252f
Reviewed-on: https://gerrit.chromium.org/gerrit/12037
Tested-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Commit-Ready: Matt Tennant <mtennant@chromium.org>
Upgraded dev-libs/elfutils to version 0.152-r1 on arm, x86.
This is step 1. Step 2 will be to enable 0.152-r1 for arm, amd64, and x86,
in chromiumos-overlay/profiles/default/linux/package.keywords.
BUG=chromium-os:21223
TEST=built x86-alex and arm-generic
Change-Id: Ia26608ff8ec49029a667f9c0fca21784a4219b50
Reviewed-on: https://gerrit.chromium.org/gerrit/11948
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Geoff Pike <gpike@chromium.org>
Tested-by: Geoff Pike <gpike@chromium.org>
Upgraded app-editors/emacs to version 23.3-r2 on amd64
BUG=None
TEST='sudo emerge -1 emacs' worked after I made these changes; if failed without them.
Change-Id: Ia2af7be79fb2459ff924adc0dcf764e1b31019db
Reviewed-on: https://gerrit.chromium.org/gerrit/11988
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
If people land upgrade hooks of the same version levels independently and
no one notices, we get into an inconsistent state where only one of the
hooks actually runs. Add a sanity check so we bail rather than upgrading
the chroot with an arbitrarily picked script.
BUG=None
TEST=run build_packages with multiple 17_xxx files in a ver 16 chroot and see script error out
TEST=run build_packages with single 17_xxx file in a ver 16 chroot and see successful run
Change-Id: If9a71f60badb7c9643c1a03ad49bb23ffb64f341
Reviewed-on: https://gerrit.chromium.org/gerrit/11972
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The bashrc that is in each board's /etc/portage/ dir is an old tool from
crossdev which we no longer use/need, so drop it. Especially since it
conflicts with newer bashrc profile stacking.
BUG=chromium-os:21276
TEST=chroot updated to 18 and all /etc/portage/bashrc files in /board/*/ are gone
Change-Id: I51688ce6c04e91506113d920bf1a50a6a822d2f3
Reviewed-on: https://gerrit.chromium.org/gerrit/11908
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=chromium-os:21244
TEST=./build_packages unmerges old grub and installs new one (with related change)
Change-Id: Iadfbd219a989f71258786591c047ace3931f1e9c
Reviewed-on: https://gerrit.chromium.org/gerrit/11951
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Tested-by: Anush Elangovan <anush@chromium.org>
The make_chroot script was upgraded to add its customizations to a file
in /etc/sudoers.d/ instead of modifying /etc/sudoers. Then the sudo
ebuild was updated to not modify /etc/sudoers anymore. This meant for
older chroots, the customizations that make_chroot added were lost in
the process.
Add an upgrade hook that creates the split /etc/sudoers.d/ file for older
chroots that did not go through the newer make_chroot.
BUG=chromium-os:11991
TEST=set chroot to 16, deleted file, ran build_packages: chroot updated to 17 and created correct /etc/sudoers.d/90_cros file
TEST=set chroot to 17, create /etc/sudoers.d/90_cros, ran build_packages: chroot updated to 17 and left existing file alone
Change-Id: I279ac3e15380e02b50a752a62cecbd94171fd724
Reviewed-on: https://gerrit.chromium.org/gerrit/11774
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=chromium-os:21244
TEST=./build_image works with both old and new grub
Change-Id: Idca80f777b7da72da1690bc374a156f910d487b0
Reviewed-on: https://gerrit.chromium.org/gerrit/11876
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Tested-by: Anush Elangovan <anush@chromium.org>
Commit-Ready: Anush Elangovan <anush@chromium.org>
The script was here to provide transitional notice to developers;
it is no longer needed.
BUG=None
TEST=None
Change-Id: Idfaae066bfb929caa306e1adbf8055a5fe4e69f5
Reviewed-on: https://gerrit.chromium.org/gerrit/11882
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
This allows KVM stage to run significantly faster. On
my machine, with this change I was able to run the pre-flight
queue VM update tests in ~369 seconds, compared to the normal
time of >1000 seconds.
BUG=chromium-os:23112, chromium-os:22784
TEST=Verify speed increase, trybot runs.
Change-Id: Ic27dd1719573fb50a412a0cfe39adf5408493ea8
Reviewed-on: https://gerrit.chromium.org/gerrit/11835
Commit-Ready: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
This is very inefficent in calling dump_syms sequentially this can be parallelized easily and reduce the time it takes (~6mins)
BUG=chromium-os:21914
TEST=./cros_generate_breakpad_symbols --board=x86-alex, amd64-corei7
Change-Id: Ic9d3bbcd2dbccfaeb01e60d757549dcb5c45c03b
Reviewed-on: https://gerrit.chromium.org/gerrit/11747
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Tested-by: Anush Elangovan <anush@chromium.org>
The qemu-kvm package had to be patched, so it was moved to the chromiumos-overlay.
This version in portage-stable is no longer needed.
BUG=chromium-os:22309
TEST=`equery which qemu-kvm` continues to not pick up this package
Change-Id: Ibe1430ca6cda86981487e1b64a127bdb147ba522
Reviewed-on: https://gerrit.chromium.org/gerrit/11717
Tested-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Matt Tennant <mtennant@chromium.org>
This disables text cursor on ttys by default to get rid of a black
rectangle showing up during but on splash screen.
BUG=chromium-os:22879
TEST=manual boot on Alex
Change-Id: I06c50034c03488e49f88e01152cdceeee4f49a24
Signed-off-by: Pawel Osciak <posciak@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/11730
Reviewed-by: Olof Johansson <olofj@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Upgraded net-libs/gnutls to version 2.10.5 on arm, x86
BUG=chromium-os:22309
TEST=`sudo emerge -1 gnutls` installs
No further testing until package is actually used by later changelist.
Change-Id: I901c74da6cabf81dfd4389a55ceb50330c010681
Reviewed-on: https://gerrit.chromium.org/gerrit/11678
Commit-Ready: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Tested-by: Matt Tennant <mtennant@chromium.org>
I will attempt to shrink this rootfs size back to the original size.
BUG=chromium-os:22932
TEST=./build_image --board=amd64-corei7 --noenable_rootfs_verification --symlink=factory_shim factory_install
Change-Id: I3bf571c569330480293f35ec3390c9ab6b76f4e2
Reviewed-on: https://gerrit.chromium.org/gerrit/11637
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Tested-by: Anush Elangovan <anush@chromium.org>
Commit-Ready: Anush Elangovan <anush@chromium.org>
The upstream Gentoo version of the gtest ebuild should cover all our
existing needs, but it also includes some build fixes which make cross
compiling work nicely (regenerating libtool to avoid relink failures).
BUG=chromium-os:21276
TEST=`emerge-arm-generic gtest` works w/out -I/-L hacks
TEST=`emerge-x86-generic gtest` still works
TEST=`emerge gtest` still works
Change-Id: Ib1de68d24523ef0f33fb1b25154d7daeb42c8ef3
Reviewed-on: https://gerrit.chromium.org/gerrit/11577
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Chris Wolfe <cwolfe@chromium.org>
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Every invocation of `sudo` delays things, so merge all of the mounts
into a single `sudo` command when possible. This saves over 1 second
on initial execution (out of ~4 seconds total).
BUG=None
TEST=`cros_sdk --enter true` still mounts & unmounts properly
Change-Id: Ibc66507dc21250a81207d2f940645eaebe93c79c
Reviewed-on: https://gerrit.chromium.org/gerrit/10901
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Current builds sometimes fail due to libtool relinking problems (having
it use -L paths to the host system instead of the sysroot). Pull in a
fix from upstream where we run elibtoolize to workaround that.
BUG=chromium-os:21276
TEST=`emerge-arm-generic udev` works w/out -I/-L hacks
TEST=`emerge-x86-generic udev` still works
TEST=`emerge udev` still works
Change-Id: I6c4e118999e125a647fa019a316d8d4ea6b6cec3
Reviewed-on: https://gerrit.chromium.org/gerrit/11535
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The current diffutils version is hanging when emerging with gcc-4.6:
diffutils-2.8.7-r2: checking for working C stack overflow detection...
Still building diffutils-2.8.7-r2 (361m17.0s). Logs in /tmp/diffutils-2.8.7-r2-tt8se3
Looks just like the upstream Gentoo bug:
https://bugs.gentoo.org/340923
Which is fixed by a newer version, so here we are.
BUG=None
TEST=`emerge-amd64-generic diffutils` worked
TEST=`emerge-arm-generic diffutils` worked
TEST=`emerge-x86-generic diffutils` worked
TEST=`emerge diffutils` worked
Change-Id: I7249f651a2c9791cee224922a9272009e4dcdec6
Reviewed-on: https://gerrit.chromium.org/gerrit/11592
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Now that the /usr/bin/awk symlink has moved to the chromeos-base package,
we can move to the unmodified upstream Gentoo ebuild.
BUG=chromium-os:21900
TEST=`emerge chromeos-base` and see /usr/bin/awk -> gawk
TEST=`emerge-amd64-generic mawk` and see /usr/bin/awk -> mawk
TEST=`emerge-arm-generic mawk` and see /usr/bin/awk -> mawk
TEST=`emerge-x86-generic mawk` and see /usr/bin/awk -> mawk
Change-Id: Ie3bf1bc321ca1c36d01fdae897172ad5f3fd695c
Reviewed-on: https://gerrit.chromium.org/gerrit/11407
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
