Specifically, do this via env for the time being since each program
doesn't necessarily have an option (nor warrant one).
BUG=None
TEST=None
Change-Id: I26e7f06ad5d6a44a7826bfa8465b34154d21b6a3
Reviewed-on: https://gerrit.chromium.org/gerrit/22295
Tested-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
This actually turns out to be a prime example of amdahls; generating
symbols for just the chrome binary takes ~120s, and with parallelization
in place for my hardware it now takes just over 120s.
For wall time, on my local hardware this brings it down from ~472 to
~120; can't get any faster w/out speeding up dump_syms itself at this
point.
The way this works is via passing the workers pid down a named pipe
once it's finished. The usual approch to bash parallelization is
a round robin loop over an array- this doesn't suffice here due
to the aforementioned chrome binary, thus the hash/control pipe
approach.
For output, we're relying on linux's atomic write gurantee for
pipes; all of our output passes through error/info/warn which
internally will chunk each line of text up into a separate
write (I517ffde4d1bb7e2310a74f5a6455b53ba2dea86c added this).
Via this approach (and the explicit check and setup if necessary
of a pipe), we don't have to worry about interleaved output.
Due to the new approch, we no longer report how much raw data
was generated; instead we report the unique end result. This
is noteworthy since both versions are generating 1742989183 bytes
of data, but the actual ondisk is 1664241402. While that is
78MB of redundant data generated, it's less than 5% of our
generated data and likely is more trouble removing than it's
worth (it won't bring the runtime down at all after all).
Finally... while I realize this is a bit more complex than
most script tricks we do, frankly this route's pretty straightforward-
while we could rewrite this into python, we run the risk of bugs
during conversion, issues w/ multiprocessing having it's own races,
and generally a bit more pain then was worth the hour to hack this
up.
BUG=chromium-os:23050
TEST=cbuildbot x86-generic-full --remote
TEST=manual runs comparing output before/after
Change-Id: I5dd0f685bbb7f5e63e6a1f998e38156b76e80582
Reviewed-on: https://gerrit.chromium.org/gerrit/21940
Commit-Ready: Brian Harring <ferringb@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>
Upgraded app-office/dia to version 0.97.2 on amd64
Needed for building documentation with some packages.
BUG=None
TEST=`emerge dia` worked
Change-Id: I47d808faaee023b816f03f15c244ee00f7af6984
Reviewed-on: https://gerrit.chromium.org/gerrit/22160
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded media-libs/libart_lgpl to version 2.3.21-r1 on amd64
Needed by dia.
BUG=None
TEST=`emerge dia` worked
Change-Id: I1cc4efa04a9d468e8f55b1bf7830d403d75d1f49
Reviewed-on: https://gerrit.chromium.org/gerrit/22159
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded virtual/pkgconfig to version 0 on amd64
Needed for new dia package.
BUG=None
TEST=`emerge dia` worked
Change-Id: I34f195906f989adea60472cafae9a61311665182
Reviewed-on: https://gerrit.chromium.org/gerrit/22158
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Add app-text/dos2unix to version 5.3.1 on amd64 in portage-stable.
This utility is meant for use within the chroot.
BUG=None
TEST=Verify dos2unix emerges and runs (sudo emerge dos2unix in chroot)
Change-Id: I2bf5b7843db99b3df40b4342f6c80d44c397ae53
Reviewed-on: https://gerrit.chromium.org/gerrit/22071
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Currently, if set -e spots a nonzero exit we basically have
no real debug information- it just stops immediately without stating
where or why. This forces our scripts to be stupidly verbose so
we can track roughly where they were, thus when they fail we can
use that information to localize the rough exit point.
Instead we should be traping that set -e induced exit and
outputing necessary debug information to run it down. This includes
outputing the relevant stack trace, or at least what we can get of
it.
The 'die' function is now enhanced to automatically dump the trace
that lead to it. For most consumers this is desired- however for
commandline parsing induced dies ("--board is missing" for example),
the trace is noise. For those cases, a 'die_notrace' function was
added that retains the original non-backtrace behaviour.
Example output via instrumenting cros_generate_breakpad_symbols
w/ the failing command '/bin/false' (nonzero exit code).
Before:
./cros_generate_breakpad_symbols monkeys --board=x86-alex
<no output at all, just exit code 1>
With this CL:
./cros_generate_breakpad_symbols monkeys --board=x86-alex
ERROR : script called: ./cros_generate_breakpad_symbols 'monkeys' '--board=x86-alex'
ERROR : Backtrace: (most recent call is last)
ERROR : file cros_generate_breakpad_symbols, line 207, called: main 'monkeys' '--board=x86-alex'
ERROR : file cros_generate_breakpad_symbols, line 163, called: die_err_trap '/bin/false' '1'
ERROR :
ERROR : Command failed:
ERROR : Command '/bin/false' exited with nonzero code: 1
BUG=chromium-os:30598
TEST=inject a failing command into a script, verify the output.
TEST=inject a 'command not found', verify the output
TEST=cbuildbot x86-generic-full --remote
TEST=cbuildbot arm-tegra2-full --remote
TEST=cbuildbot chromiumos-sdk --remote
Change-Id: I517ffde4d1bb7e2310a74f5a6455b53ba2dea86c
Reviewed-on: https://gerrit.chromium.org/gerrit/17225
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
This allows us to specify a boost size where we know we are growing Chrome,
but don't know what the default sizes are, nor whether we are overriding them
elsewise.
BUG=chromium-os:29829
TEST=try(lumpy-chrome-pfq,lumpy-canary)
Change-Id: I3b7c927874fdfedace027e7a2398d9e97a9d3527
Reviewed-on: https://gerrit.chromium.org/gerrit/21519
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Peter Mayo <petermayo@chromium.org>
Tested-by: Peter Mayo <petermayo@chromium.org>
This is a straightforward change- the intent is to up the debug
information available so we can deal w/ crashes like:
http://chromegw.corp.google.com/i/chromeos/builders/x86-alex32%20canary/builds/56
BUG=None
TEST=# Manual inducing of failures.
Change-Id: Ibea75d1467160fc7f07c21235d701692cec96d05
Reviewed-on: https://gerrit.chromium.org/gerrit/21931
Reviewed-by: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Of the 11713 lines output via this for a mario build, 96% of it
is stating "Using dump_syms.32 for 32-bit file <the-path>".
At one point that may have been useful; now it just obscures errors,
thus only output that info when verbose is turned on.
BUG=None
TEST=./cros_generate_breakpad_symbols; # enjoy the 438 lines of
# output rather than the 11,700 lines of output.
Change-Id: Iba9d1af3421c6b377af8388446521d106399ce25
Reviewed-on: https://gerrit.chromium.org/gerrit/21925
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
We intended to use some extra python modules for autotest in the chroot,
but decided against it. They're removed from hard-host-depends in
https://gerrit.chromium.org/gerrit/21816
BUG=None
TEST=./upgrade_chroot; see that they've been removed.
CQ-DEPEND=If896436bf9fed7c0fd600ffca9a4c854fd7eceba
CQ-DEPEND=I95df39e40b62c919df0bafcb490d8caa48c04dd4
Change-Id: If9854661b8774d519c5a587e77c31eafdc9b889b
Reviewed-on: https://gerrit.chromium.org/gerrit/21817
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
This CL updates profiles/updates/3Q-2010 to indicate that
sys-apps/parted has been moved to sys-block/parted.
BUG=chromium-os:30350
TEST=cbuildbot --remote {x86-generic,amd64-generic,arm-tegra2}-paladin
Change-Id: I380363843c2cffde246c4642e49f683c4803636e
Reviewed-on: https://gerrit.chromium.org/gerrit/21784
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
These shouldn't be around anymore, so let's move them.
BUG=None
TEST=build_packages for x86-alex worked
Change-Id: I95df39e40b62c919df0bafcb490d8caa48c04dd4
Reviewed-on: https://gerrit.chromium.org/gerrit/21806
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Resubmit of If62b4f3973f02fd8e1deed35864c824a02ab0c22
This will be safe to land after I2c4e21ec7e8c0c0cf58947e2b0a3a9edf7617a09
It is now used for:
- make_chroot (cros_sdk --bootstrap)
- update_chroot
setup_board is stripped of redundant code which was deprecated by this.
Also stripped is some usepkg logic in make_chroot, as that is now
exclusively source-only.
BUG=chromium-os:23032
TEST=trybot chromiumos-sdk
Change-Id: Ic908eac712ac097e5c2062d3be70177e172aa924
Reviewed-on: https://gerrit.chromium.org/gerrit/20191
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Zdenek Behan <zbehan@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
This CL imports sys-block/parted-3.1 from upstream, which will not be
used until all packages that depend on sys-apps/parted are switched to
depend on sys-block/parted.
parted-3.0 was previously imported, but due to a crash in partprobe,
parted-3.1 is imported to resolve the issue.
BUG=chromium-os:30350
TEST=Tested the following:
1. `emerge-{x86,amd64,arm}-generic parted` still builds
sys-apps/parted-1.9.0-r1
2. `emerge-{x86,amd64,arm}-generic sys-block/parted` builds
sys-block/parted-3.1 successfully after
`emerge --unmerge sys-apps/parted`
Change-Id: I41ffe6a08184a3d3a1c9c64c96da57077120a08d
Reviewed-on: https://gerrit.chromium.org/gerrit/21705
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Using /proc/mounts is safer because mtab may in rare cases get desynced.
The only significant difference in output is "X Y" instead of "X on Y".
BUG=chromium-os:30249
TEST=create a chroot; enter a chroot; exit a chroot
TEST=assortment of manual tests
Change-Id: I392290e6f52a677ee2d77d77e025ef60240b11b5
Reviewed-on: https://gerrit.chromium.org/gerrit/21499
Tested-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Zdenek Behan <zbehan@chromium.org>
This CL imports sys-block/parted-3.0 from upstream, which will not be
used until all packages that depend on sys-apps/parted are switched to
depend on sys-block/parted.
BUG=chromium-os:30350
TEST=Tested the following:
1. `emerge-{x86,amd64,arm}-generic parted` still builds
sys-apps/parted-1.9.0-r1
2. `emerge-{x86,amd64,arm}-generic sys-block/parted` builds
sys-block/parted-3.0 successfully after
`emerge --unmerge sys-apps/parted`
Change-Id: Ic2e22caa9e214cc6aaa0433b8b319bbb56d94f4c
Reviewed-on: https://gerrit.chromium.org/gerrit/21638
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
jstest is useful for testing.
BUG=chromium-os:30273
TEST=emerge-$BOARD games-util/joystick
Change-Id: I5a79a5dbf5ea2e65899524f4c47a2f1cfecb3f05
Reviewed-on: https://gerrit.chromium.org/gerrit/21549
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
The private chromeos-overlay has shared credentials for read-only
access to the archive of CrOS images. When entering the chroot check
whether these credentials are available, and install them to ~/.boto
within the chroot unless that file already exists.
BUG=None
TEST=Applied patch and entered fresh private and public chroots.
Manually ran 'gsutil config' to replace the credentials;
this works as long as there is no ~/.boto.bak already.
Re-entered the chroot with manually-configured credentials.
Ran 'gsutil ls' with BOTO_CONFIG set to a board-specific boto.
Change-Id: Ib62dc28f90bce692a833b5fc9d4c56981acc98d1
Reviewed-on: https://gerrit.chromium.org/gerrit/21480
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Chris Wolfe <cwolfe@chromium.org>
Commit-Ready: Chris Wolfe <cwolfe@chromium.org>
Upgraded app-arch/gzip to version 1.4 on amd64, arm, x86
We don't need the old style virtual anymore as upstream has dropped it.
Note: With the dependent CL merged, this should no longer break the tree.
BUG=None
TEST=`cbuildbot chromiumos-sdk` worked
Change-Id: Ib104eab1f7a73ab37d0a892425ec413ed69bfda2
CQ-DEPEND=I2f57f44d1121c47ba9ae26d5a113d73e6aa47723
Reviewed-on: https://gerrit.chromium.org/gerrit/20933
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The unmodified version works for us, so import it from upstream Gentoo
rather than having our own copy in chromiumos-overlay/.
BUG=chromium-os:25177
TEST=`emerge-x86-alex libv4l` still works
Change-Id: I64744d1f820cc06062b3376176db292aeb82793c
Reviewed-on: https://gerrit.chromium.org/gerrit/21340
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded sys-apps/pciutils to version 3.1.9-r1 on amd64
BUG=chromium-os:29910
TEST=run in chroot
% USE="static static-libs" emerge-x86-alex flashrom
Change-Id: I1a5065be0938ad964ac5c6319fe50fa164970708
Reviewed-on: https://gerrit.chromium.org/gerrit/21017
Reviewed-by: Yung-Chieh Lo <yjlou%chromium.org@gtempaccount.com>
Tested-by: Yung-Chieh Lo <yjlou%chromium.org@gtempaccount.com>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Upgraded dev-python/requests to version 0.11.1 on amd64
Upgraded dev-python/chardet to version 2.0.1 on amd64
Upgraded dev-python/certifi to version 0.0.8 on amd64
BUG=chromium-os:29730
TEST=trybot
Change-Id: I0dbd13d80710d37c7393e020e0dc8c6af106f33d
Reviewed-on: https://gerrit.chromium.org/gerrit/21275
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
BUG=none
TEST='emerge-arm-generic chromeos-test'
Change-Id: I67bfc8dfdc908c0b8ea0c7e001e1117d264bdb32
Reviewed-on: https://gerrit.chromium.org/gerrit/21247
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
emacs depends on this
Upgraded virtual/emacs to version 23 on amd64
BUG=chromium-os:30047
TEST=None
Change-Id: Ie4e2b0ef336de3cfac937594b033b6296cf7845b
Reviewed-on: https://gerrit.chromium.org/gerrit/21185
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
We have pretty good binpkg support for chrome now, as well as incremental
building (and ccaching), so we should be able to drop this flag now.
BUG=None
TEST=build_packages still works for x86-alex
Change-Id: I3f3bf7e513ef45c091cc8363753035cac07d2f97
Reviewed-on: https://gerrit.chromium.org/gerrit/20967
Reviewed-by: Anush Elangovan <anush@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This CL adds 'arm' keyword to dev-python/pexpect, which is needed to
support servo serial console communication.
BUG=chromium-os:29907
TEST='emerge-tegra2 pexpect'
Change-Id: I5a74069d77ef28d6830ffb34291d09fe89333513
Reviewed-on: https://gerrit.chromium.org/gerrit/21199
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
To avoid looking like we're DoS'ing the symbol server, force a delay between
symbol uploads. If this becomes a bottleneck for buildbots, this should be
modified to only upload symbol files that have changed, by checking against
the buildbot's previous debug.tgz.
BUG=chromium-os:26596
TEST=Manually ran upload_symbols against staging symbol server
Change-Id: Iecf11e26a70f0c44838fb13e2ebc6ebb78336c50
Reviewed-on: https://gerrit.chromium.org/gerrit/19566
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
We also need the jre/jdk virtuals to make this work. The packages those
virtuals depend on have already been merged.
BUG=None
TEST=`emerge closure-compiler-bin && closure-compiler --help` works
Change-Id: I766e27d74c0b61014613105e2958c3a6d87d8a50
Reviewed-on: https://gerrit.chromium.org/gerrit/20966
Reviewed-by: Jon Salz <jsalz@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Delay up to 63 seconds when trying to upload a symbol file. My default of
15 seconds before turned out to not be enough to cover at least one case
that davidjames@ found in ToT buildbots.
BUG=chromium-os:29963
TEST=Ran upload_symbols --testing
Change-Id: I82b038f8845c3f2aaba0ee95f40efd4b70e2ffb1
Reviewed-on: https://gerrit.chromium.org/gerrit/21016
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
This reverts commit bc856858be86b1ae7c4dc33b256f43baac51636d
The thing is that ${FLAGS_board} is not set when build_kernel_image.sh runs, so the check never kicks in.
Change-Id: I501cb979c7aef8d2f7061da2b6cf2daedfe65004
Reviewed-on: https://gerrit.chromium.org/gerrit/20977
Tested-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Ready: Vadim Bendebury <vbendeb@chromium.org>
Upgraded media-libs/lcms to version 2.3 on amd64, arm, x86
Needed for virtual/jpeg usage.
Note: this has to merge with the ghostscript-gpl change to work.
BUG=chromium-os:25177
TEST=`cbuildbot chromiumos-sdk` works
TEST=build_packages+build_image for x86-alex boots & runs fine
Change-Id: I2f19a0e1b35d288acca834ecb7890db3e2509149
Reviewed-on: https://gerrit.chromium.org/gerrit/20975
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded media-libs/jbig2dec to version 0.11-r1 on amd64, arm, x86.
Needed for lcms upgrade which is needed for virtual/jpeg.
BUG=chromium-os:25177
TEST=`cbuildbot chromiumos-sdk` works
Change-Id: Id7fe53517357ff34fd2df02313ead8c151007297
Reviewed-on: https://gerrit.chromium.org/gerrit/20617
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded dev-python/pexpect to version 2.4 on amd64
BUG=chrome-os:29907
TEST='emerge dev-python/pexpect' succeeded.
TEST=Use pexpect to communicate with serial console.
Change-Id: I0cf1abdef97f245afd334f2532d3fea398bcaaa0
Reviewed-on: https://gerrit.chromium.org/gerrit/20907
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Vic Yang <victoryang@chromium.org>
Tested-by: Vic Yang <victoryang@chromium.org>
Upgraded dev-python/ws4py to version 0.2.1-r2 on amd64, arm, x86
BUG=None
TEST=Built Chrome factory UI
Change-Id: I98509cbc1643413f4bb8c3096ad512c7e86beeeb
Reviewed-on: https://gerrit.chromium.org/gerrit/20928
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Jon Salz <jsalz@chromium.org>
Commit-Ready: Jon Salz <jsalz@chromium.org>
Upgraded dev-python/jsonrpclib to version 0_pre20110820-r1 on amd64, arm, x86
BUG=None
TEST=Built/ran factory UI with Chrome
Change-Id: I25cc02de50264f8dd2f98ca89badb14a4a9fb445
Reviewed-on: https://gerrit.chromium.org/gerrit/20871
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Jon Salz <jsalz@chromium.org>
Tested-by: Jon Salz <jsalz@chromium.org>
This reverts commit 8bc7c957f81c7783fb502649df90a85ec2bcd616
Upgrading gzip broke the tree because it accidentally caused
gzip to no longer be included in the chroot.
BUG=chromium-os:29828
TEST=Remote trybot run.
Change-Id: Icc27b38414dbabb3714998ef310472b7a9823b45
Reviewed-on: https://gerrit.chromium.org/gerrit/20803
Reviewed-by: Peter Mayo <petermayo@chromium.org>
Tested-by: David James <davidjames@chromium.org>
Upgraded media-libs/lcms to version 2.3 on amd64, arm, x86
Needed for virtual/jpeg usage.
BUG=chromium-os:25177
TEST=`cbuildbot chromiumos-sdk` works
TEST=build_packages+build_image for x86-alex boots & runs fine
Change-Id: I0beffcd73649bebf3abb5702ee869c663d1141aa
Reviewed-on: https://gerrit.chromium.org/gerrit/20512
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded media-libs/tiff to version 4.0.0-r1 on amd64, arm, x86
Needed for virtual/jpeg usage.
BUG=chromium-os:25177
TEST=`cbuildbot chromiumos-sdk` works
TEST=build_packages+build_image for x86-alex boots & runs fine
Change-Id: I59da1cf30336d6016fbb2cd08f19d4fb32464ebb
Reviewed-on: https://gerrit.chromium.org/gerrit/20513
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upgraded app-arch/gzip to version 1.4 on amd64, arm, x86
We don't need the old style virtual anymore as upstream has dropped it.
BUG=None
TEST=`cbuildbot chromiumos-sdk` worked
Change-Id: Id2d4950cd92fed4bb904eef5a9b070ad2d38041f
Reviewed-on: https://gerrit.chromium.org/gerrit/20493
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
If the symbol file to be uploaded to the symbol server is close to the limit
at which the symbol server will reject it, show an error so we can do
something about it before it's too late. This also prints the special
"@@@STEP_WARNINGS@@@" line to make the buildbot show the step as orange.
BUG=chromium-os:19194
TEST=Manually ran upload_symbols to make sure it worked with/without an error
Change-Id: I7942ba20f7bc83d66036f9f9fe66403083b1a1f1
Reviewed-on: https://gerrit.chromium.org/gerrit/20664
Commit-Ready: Michael Krebs <mkrebs@chromium.org>
Tested-by: Michael Krebs <mkrebs@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Upgraded media-libs/jbig2dec to version 0.11-r1 on amd64, arm, x86.
The current ghostscript-gpl ebuild has been bundling jbig2dec, but
with the latest versions (follow up CL), it uses the system one.
BUG=chromium-os:25177
TEST=`cbuildbot chromiumos-sdk` works
Change-Id: I64ef9325386427472c8d34e21e2b9fafe4a943e0
Reviewed-on: https://gerrit.chromium.org/gerrit/20616
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
