https://chromium-review.googlesource.com/c/chromium/tools/build/+/988694/
will turn it on for the simple chrome bots (Right now they invoke all of
gclient inside the chrome-sdk.)
Bug: 732531, 828392
Change-Id: I1f892970cd19fd8f64dcfb6615d3033301ac2fcb
Reviewed-on: https://chromium-review.googlesource.com/989235
Commit-Queue: Benjamin Pastene <bpastene@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#547812}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 9d8ac1b4c1fe49b249575ed7d935fc533b720eb1
Useful for people where the linux installation doesn't provide it by
default, and for bots.
I copied the system ciopfs binary on my ubuntu trusty box to build/ciopfs
and ran:
upload_to_google_storage.py -b chromium-browser-clang/ciopfs build/ciopfs
Bug: 808098
Change-Id: Ia6dd7548a5a5761898506f6bbe50625c33151988
Reviewed-on: https://chromium-review.googlesource.com/897890
Reviewed-by: Scott Graham <scottmg@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#533804}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 762993055a75a8f62232e5454f16b566a2de7e3c
The eu-strip that ships with Ubuntu Trusty segfaults when stripping a
chrome binary that statically links libc++. The issue was fixed
upstream at some point because the crash does not occur on Ubuntu
Xenial.
This CL bundles a patched eu-strip for x86_64 (and removes the x86 one
that used to be in Google Cloud Storage).
The issue was due to a double-free in libelf.so. The patched version
simply removes the offending call to free and statically links libelf
into eu-strip. This probably results in a memory leak, but this is ok
for now since the utility is a very short-lived process.
BUG=593874
R=dpranke@chromium.org,thestig@chromium.org
TBR=thakis@chromium.org
Change-Id: I2085c4f6278cffbaeae972545280ebb437a8bdc0
Reviewed-on: https://chromium-review.googlesource.com/544798
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#481710}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 4312d5e0b01af9a3ad5f92a1763142155f01a7c6
This will be used primarily on perf bots to download APKs used for
tracking per-milestone patch size growth.
BUG=695188
Review-Url: https://codereview.chromium.org/2750603003
Cr-Original-Commit-Position: refs/heads/master@{#456502}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 2850476323ae769b612011f3d99a2d17759a2952
Having this, a lot of wasted bandwidth is avoided for projects
that use these directories as DEPS entries, since the top-level
Chromium .gitignore doesn't exist in those cases.
The src/ repo already contained 51 other .gitignore files anyway,
so it's hard to claim the top-level file has to be the only one.
BUG=690010
Review-Url: https://codereview.chromium.org/2710593005
Cr-Original-Commit-Position: refs/heads/master@{#452167}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 68d02518d39937443244001624fa500e00aad408