Upstream guava has switched to full and -android versions. We should
also switch to it due to incompatibilities with dexing. Future versions
of third_party/auto will need full guava 21+ and other third_party
libraries need the android version.
Also added some cipd instructions, these may be outdated soon but are
useful in the meantime.
Bug: None
Change-Id: I7f15368664fbbbd7950feb38d978aa251effa354
Reviewed-on: https://chromium-review.googlesource.com/871870
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#530168}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 4689398543791657407ef2e12446865cb995a633
CL:843774 made us download these profiles for Chromium and subprojects
(e.g. webrtc). We don't (yet?) want to apply profiles to said
subprojects, so we shouldn't be pulling them in the first place.
Bug: 799064
Test: AFDO build of apks/Chrome.apk (among others) succeeds
Change-Id: Id1d34e1cc442c4871191f47564d6b625cce36f42
Reviewed-on: https://chromium-review.googlesource.com/851068
Commit-Queue: George Burgess <gbiv@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#528237}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: bfc93d720491020defa4573a0d4da4ac7918e700
Scrubbed Chrome OS profiles (well, one at the moment) live in
chrome/android/profiles. Hopefully we won't need to scrub them soon.
In order to do AFDO on Chromium, we need to pull them locally.
size wins are observed as with unscrubbed profiles on Chrome.apk
(assuming the profile actually gets turned on, which is moved to
another patch).
Bug: 794750
Test: ChromePublic.apk builds after `gclient sync`. Similar perf/binary
Change-Id: I9cc034ca21e948b372944b6bcdc8c5055fd71ca8
Reviewed-on: https://chromium-review.googlesource.com/843774
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#526794}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: c8ff4dc41dd0ce87cb0ac8d7f31c7b373e1af574
This reverts commit 0f06f8fdd7a74985f65e28b79539916f94e85eac.
Reason for revert: CIPD doesn't allow multiple .ensure files to coexist, crbug.com/789809
Original change's description:
> Fuchsia: use CIPD to check out arch-specific QEMU binaries.
>
> These binaries allow us to run QEMU on ARM; the current deployment
> in the Fuchsia SDK folder is x86-64 only.
>
> The "qemu" folder can safely be removed from the Fuchsia SDK
> once this CL lands and the trybots are confirmed to still be in
> working order.
>
> Also modify the runner script to use arch-specific QEMU binaries.
>
>
> Bug: 786193
> Change-Id: I1515bdf330f496ff47f88ba3b131629d4e24fea3
> Reviewed-on: https://chromium-review.googlesource.com/783699
> Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
> Reviewed-by: Dirk Pranke <dpranke@chromium.org>
> Reviewed-by: Scott Graham <scottmg@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#519536}
TBR=dpranke@chromium.org,kmarshall@chromium.org,scottmg@chromium.org
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 786193
Change-Id: I320cf80f222c337b38e91e0f10ef2a3479f45f9d
Reviewed-on: https://chromium-review.googlesource.com/810088
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#521990}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: c63a098c3d847b0aa9b21c510b57d112278d0c21
These binaries allow us to run QEMU on ARM; the current deployment
in the Fuchsia SDK folder is x86-64 only.
The "qemu" folder can safely be removed from the Fuchsia SDK
once this CL lands and the trybots are confirmed to still be in
working order.
Also modify the runner script to use arch-specific QEMU binaries.
Bug: 786193
Change-Id: I1515bdf330f496ff47f88ba3b131629d4e24fea3
Reviewed-on: https://chromium-review.googlesource.com/783699
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Scott Graham <scottmg@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#519536}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 0f06f8fdd7a74985f65e28b79539916f94e85eac
With Robolectric 3.4.2, we can nearly run vanilla, only requiring
the following modifications:
- we need to have a stub impl of MavenDependencyResolver since there
is no point to adding the third-party Maven jars to Chromium.
- we need to have some files which are generated by Robolectric
annotation processor during compile time. GN makes it
difficult to use these auto-gen files during the build.
This also rolls findbugs to pick up a GN change required to expose a
JAR for 3.4.2.
Bug: 729135
Change-Id: I3e80b532bd88ba6a40b64eb935a31f52cc20588f
Reviewed-on: https://chromium-review.googlesource.com/709469
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Changwan Ryu <changwan@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#515606}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 79bf00ad560f5eb18998655911a0610b545a3c7b
This reverts commit a4e8c9b8060b47634b0862802d25a48304ce3110.
Reason for revert: Android only change, breaking important Android bots.
Bug: 755920
Original change's description:
> Switch Android binary deps to be managed by CIPD.
>
> Removing b/a/update_deps/update_third_party_deps.py script.
> Replacing with a simple CIPD wrapper script.
>
> Adding ensure files for all each target_os (this is a file used to
> describe the package you want to download). Initially, this is just
> Android.
>
> Adding cipd.yaml files for all deps (this file was used to
> create the CIPD packages), and can be modified/used in the future
> to update these deps.
>
> CIPD gives us the advantage of having a consistent method of
> downloading/managing our binary dependencies. The goal is to move
> as much as possible from adhoc scripts over to CIPD. CIPD does
> various nice things, such as verifying the integrity of the fetched
> binary and doing smart caching. What our adhoc scripts do currently
> is very inconsistent.
>
> Bug:
> Change-Id: Iccf7defe80c8548e6929d994595e841aa4668c92
> Reviewed-on: https://chromium-review.googlesource.com/544524
> Commit-Queue: Michael Case <mikecase@chromium.org>
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Reviewed-by: Grace Kloba <klobag@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#494588}
TBR=iannucci@chromium.org,klobag@chromium.org,mikecase@chromium.org,yolandyan@chromium.org,jbudorick@chromium.org
Change-Id: Id5541cc7838ad3ad9883db05b1f0b363a40569c9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/616681
Reviewed-by: Benoit L <lizeb@chromium.org>
Commit-Queue: Benoit L <lizeb@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#494740}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 0a47fd18721b7d866f4d0a3eae94f4697592b178
Removing b/a/update_deps/update_third_party_deps.py script.
Replacing with a simple CIPD wrapper script.
Adding ensure files for all each target_os (this is a file used to
describe the package you want to download). Initially, this is just
Android.
Adding cipd.yaml files for all deps (this file was used to
create the CIPD packages), and can be modified/used in the future
to update these deps.
CIPD gives us the advantage of having a consistent method of
downloading/managing our binary dependencies. The goal is to move
as much as possible from adhoc scripts over to CIPD. CIPD does
various nice things, such as verifying the integrity of the fetched
binary and doing smart caching. What our adhoc scripts do currently
is very inconsistent.
Bug:
Change-Id: Iccf7defe80c8548e6929d994595e841aa4668c92
Reviewed-on: https://chromium-review.googlesource.com/544524
Commit-Queue: Michael Case <mikecase@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Grace Kloba <klobag@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#494588}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: a4e8c9b8060b47634b0862802d25a48304ce3110
John Budorick
Andrew Grieve
Peter Wen
George Burgess IV
Kevin Marshall
Benoit L
Mike Case