Age | Commit message (Collapse) | Author |
|
This crosperf wrapper allows the user to lock devices by board
type. It will query the swarm using the crosfleet API to find
and lock an appropriate board.
The remaining arguments are passed to crosperf, so the command
will act like crosperf otherwise, once the remote has been set.
One limitation is that this wrapper does not conduct any SSH
port forwarding (which would be required for flashing
devices from a cloudtop, for example).
BUG=b:187535367
TEST=crosperf_autolock.py --board chell chell_exp.exp
Change-Id: If8dc4630c42be63d6427716654e7dd7fa4132df5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3221950
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Jordan R Abrahams <ajordanr@google.com>
Tested-by: Jordan R Abrahams <ajordanr@google.com>
|
|
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: Ia538fab15c409b67bfe21de04db3dc3a1e4ab544
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3228899
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Auto-Submit: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Denis Nikitin <denik@chromium.org>
Reviewed-by: Denis Nikitin <denik@chromium.org>
|
|
Currently, these crosperf files do not abide by the pep8 standard
that CrOS requires. This applies the necessary formatting to
get past the commit hook.
BUG=None
TEST=CQ (formatting)
Change-Id: I501fd37f8a1d20fd0b987587eb52eb582f18c1a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3215085
Tested-by: Jordan R Abrahams <ajordanr@google.com>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Jordan R Abrahams <ajordanr@google.com>
|
|
This global experiment setting prevents crosperf from
attempting to lock the associated devices. This is important
if the devices were locked previously before by crosfleet.
BUG=b:187535367
TEST=CQ
TEST=Lease board from crosfleet. Forward SSH port. Run crosperf on
forwarded port.
Change-Id: I0f5341e07e325a613c6316778c0f096f6d8088a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3210525
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Jordan R Abrahams <ajordanr@google.com>
Commit-Queue: Jordan R Abrahams <ajordanr@google.com>
|
|
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: Ie0f2728c1a4800dbfe1f8f98ec98c73a6d8a33a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3214700
Reviewed-by: Bob Haarman <inglorion@chromium.org>
Commit-Queue: Denis Nikitin <denik@chromium.org>
Tested-by: Denis Nikitin <denik@chromium.org>
|
|
This CL moves flags added for LLVM Next that disabled
variable_unused_but_set warnings to PostFlags in order to make sure it
gets added after Wall and Wextra.
BUG=b:195433889
TEST=reran package tests
Change-Id: Icdd2cbe3ced7b8427257c87f9e527b0d0e8da57d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3214640
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Ryan Beltran <ryanbeltran@chromium.org>
Tested-by: Ryan Beltran <ryanbeltran@chromium.org>
|
|
Give a warning if clang-tidy used more than TIDY_TIMEOUT/2 seconds.
Users can fix it before it gets worse and times out.
BUG=b:199451930
TEST=Use a fake Android clang-tidy.real binary,
TEST=to dump passed environment variables and run for required time.
Change-Id: I8df7e4e3bb621cbf40094c7b97494e5978d7c6a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3200220
Reviewed-by: Chih-Hung Hsieh <chh@google.com>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
|
|
This adds a few extra steps to rust_uprev where rust sources and
rust-bootstrap prebuilts are fetched from the local mirror. This
ensures that these files exist and are readable, and that the
local versions (that will be used to compute the digests for the
manifest) match the ones on the mirror.
BUG=None
TEST=Ran the script with existing and non-existing rust versions
Change-Id: I9868b027356cf14fc10d9e56665c74ad26555345
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3182632
Tested-by: Bob Haarman <inglorion@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Bob Haarman <inglorion@chromium.org>
|
|
Add a list of skipped chromium branches and adjust canary branch number
calculation.
BUG=None
TEST=`./update_kernel_afdo` shows 96 as canary.
Change-Id: If96711f5a0d52c128d4829e338b9b950001c6e75
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3199488
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Denis Nikitin <denik@chromium.org>
Commit-Queue: Denis Nikitin <denik@chromium.org>
|
|
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: Ibb3548142490b8a8277bd09eb2b53365c43507e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3200213
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Denis Nikitin <denik@chromium.org>
Tested-by: Denis Nikitin <denik@chromium.org>
|
|
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: I0990d136a0307c14242b95a0b7e7e158c7318d91
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3183335
Tested-by: Denis Nikitin <denik@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Denis Nikitin <denik@chromium.org>
|
|
rust_uprev uses `equery w` to find the ebuild file for a package.
This depends on filesystem state and so should not affect the test.
This change mocks these calls so that they return specified values
instead of actually running commands and accessing the filesystem.
BUG=None
TEST=Ran the tests outside the chroot, where equery does not exist
Change-Id: Id48a0e063f9bf112888d378d549420f008fdcb4f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3182629
Tested-by: Bob Haarman <inglorion@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Michael Benfield <mbenfield@google.com>
Commit-Queue: Bob Haarman <inglorion@chromium.org>
|
|
Update chromeos-kernel-3_18
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: I2762c38bcc24070660de24a349f5829a7436a3b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3171121
Reviewed-by: Denis Nikitin <denik@chromium.org>
Commit-Queue: Ryan Beltran <ryanbeltran@chromium.org>
Tested-by: Ryan Beltran <ryanbeltran@chromium.org>
|
|
Remove 3.18 from the kernel AFDO update.
BUG=b:199787442
TEST=./update_kernel_afdo
Change-Id: I343d2048fb6bbd9c3c9f37bdfe64526a91c68220
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3162669
Tested-by: Denis Nikitin <denik@chromium.org>
Reviewed-by: Bob Haarman <inglorion@chromium.org>
Commit-Queue: Denis Nikitin <denik@chromium.org>
|
|
BUG=b:200542097
TEST=None
Change-Id: I82f4011d499b323a4eceda2949e103dc1559299f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3171413
Commit-Queue: Jaques Clapauch <jaquesc@google.com>
Commit-Queue: Chris McDonald <cjmcdonald@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: Jaques Clapauch <jaquesc@google.com>
Auto-Submit: Jaques Clapauch <jaquesc@google.com>
Reviewed-by: Chris McDonald <cjmcdonald@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
This tool lets you work with large swaths of seccomp files quickly,
determining which have missing syscalls, and allowing fast editing
for all of them.
BUG=None
TEST=cd mass_seccomp_editor; python3 -m unittest
TEST=Ran many times for glibc noexec patch
Change-Id: I7dbad6eff431d41e23d31465a444b209520e953a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3101468
Tested-by: Jordan R Abrahams <ajordanr@google.com>
Auto-Submit: Jordan R Abrahams <ajordanr@google.com>
Commit-Queue: George Burgess <gbiv@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
Apparently some upstream conventions use `test_${x}.py` instead of this
repo's standard of `${x}_(test|unittest).py`. Either seems fine, and
supporting both seems simple.
This includes some formatting updates from yapf.
BUG=None
TEST=`./run_tests_for.py llvm_tools/*.py`
TEST=Made a new test_foo.py script; saw that it was picked up.
Change-Id: I533a9395227d8342411cacfbd1bb6d5c63b8ec2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3163797
Reviewed-by: Jordan R Abrahams <ajordanr@google.com>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
Updating to rust-1.55.0 required a few changes to rust_uprev:
- patches for rust-bootstrap no longer need to be renamed and
removed.
- the version sequence is now RUST_RAW_FULL_BOOTSTRAP_SEQUENCE
BUG=None
TEST=created uprev for rust-1.55
Change-Id: I56a64d5fd7902e01ee2ca3c13dcfc3eee52d6fc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3162670
Tested-by: Bob Haarman <inglorion@chromium.org>
Commit-Queue: Bob Haarman <inglorion@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
* To check in upstream chromeos tools.
* In Android mode, for clang-tidy, call
runAndroidClangTidy to handle TIDY_TIMEOUT
* Add runWithTimeout to env.go and runCmdWithTimeouit to command.go.
BUG=b:199451930
TEST=Use a fake Android clang-tidy.real binary,
TEST=to dump passed environment variables and run for required time.
Change-Id: I629ae372251c034595011ef70559f8b12ed8568c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3162668
Reviewed-by: Chih-Hung Hsieh <chh@google.com>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
|
|
The history of this test looks weird. We've had it intermittently
enabled/disabled depending on whether we're passing flags specifically
to llvm-next versions of clang. At the moment, it's failing due to a
lack of `-Wl,-z,nostart-stop-gc`, which was removed in a previous CL.
BUG=None
TEST=go test
Change-Id: I4b1ab9e5d39ba0e5575f89f51e4e83afba24a025
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3162667
Reviewed-by: Ryan Beltran <ryanbeltran@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
Tests are failing at HEAD; looks like prior changes forgot to update
these.
BUG=None
TEST=go test
Change-Id: Ia88b182ba0a922807f0857d8dc3df96de4528aa7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3162666
Reviewed-by: Ryan Beltran <ryanbeltran@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
The cros_logging module is deprecated and all usages are being removed.
The lint referred to by the comment removed in this CL is no longer a
thing, so remove this mention of the deprecated module from the tree.
BUG=b:191490453
TEST=None
Change-Id: Ifcd4cb18e87fdbd3a92747b0fdbac434d51fd055
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3161649
Tested-by: Chris McDonald <cjmcdonald@chromium.org>
Auto-Submit: Chris McDonald <cjmcdonald@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
This CL disables no-unused-but-set-variable warnings globally in the
compiler wrapper. A seperate CL will specifically reenable this warning
for platform2. This prevents breakage do to unised variables in
third_party.
BUG=None
TEST=None
Change-Id: I2ea44b6249715d3b036843b13d668d50b9b7669d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3150656
Tested-by: Ryan Beltran <ryanbeltran@chromium.org>
Auto-Submit: Ryan Beltran <ryanbeltran@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
|
|
The CrOS toolchain team has seen changes over the last ~year and a half.
This CL updates this file to match the current toolchain team.
BUG=None
TEST=None
Change-Id: I65e08922bb91fd5634e30c1e717fe28e62c68ce6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3133551
Reviewed-by: Ryan Beltran <ryanbeltran@chromium.org>
Reviewed-by: Christopher Di Bella <cjdb@google.com>
Reviewed-by: Jordan R Abrahams <ajordanr@google.com>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Michael Benfield <mbenfield@google.com>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
Starting tonight, an alias for the mail-sheriff program will be
mail-detective. Swap to that.
This includes forced auto-style-fixing from yapf.
BUG=b:198446837
TEST=None
Change-Id: I8f7375347c17095a7d53408617f8e46078f3db54
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3137913
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
Now that our backend for this supports detective as an alternate
spelling of sheriff, we can migrate this.
This includes forced auto-style-fixing from yapf.
BUG=b:198446837
TEST=Unittests
Change-Id: Ib371911a006d40149dfbf91cc5daf834066a451c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3137202
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
BUG=b:194845241
TEST=emerge-atlas harfbuzz
Change-Id: I262883ee20ed0fc69fcc3bf119d3068f4cf7729b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3061363
Tested-by: Jian Cai <jiancai@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
upstream-workon is a script which aids toolchain developers by
keeping the local, fully patched source in some non-ephemeral
local directory inside the chroot.
At the moment, it's still in a prototype phase (the end goal
would be to make it quite a bit safer, and also move it out of
bash).
This is the first commit for the script, meant to act as a
base for future work.
BUG=b:186803200
TEST=mkdir ~/llvm; upstream_workon.bash init sys-devel/llvm ~/llvm
TEST=upstream_workon.bash build sys-devel/llvm
TEST=upstream_workon.bash install sys-devel/llvm
TEST=upstream_workon.bash link sys-devel/llvm ~/llvm_src_tree
Change-Id: Ifa1b1520d621cbe8b435d4ebb1ae71dc28548fcf
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3068075
Commit-Queue: Jordan R Abrahams <ajordanr@google.com>
Tested-by: Jordan R Abrahams <ajordanr@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
This CL implements updating the llvm major version in non-llvm ebuilds.
An example of the current behavior (which uprevs the major version only
for the LLVM ebuild) can be seen here:
https://crrev.com/c/3080644/2
BUG=b:196193631
TEST=./update_chromeos_llvm_hash_unittest.py
Change-Id: Icf82f0a8a4a01b255d0eeb242fe139aaa6957920
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3088319
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Ryan Beltran <ryanbeltran@chromium.org>
Tested-by: Ryan Beltran <ryanbeltran@chromium.org>
|
|
We recently had to swap from a base style of Chromium to Pep8, since the
former has been removed from yapf. Apparently this wasn't a complete
nop. Keep the existing indent width.
The other changes implied by the pep => yapf transition can probably be
fixed up incrementally.
BUG=None
TEST=yapf'ed a random file
Change-Id: I736b61c413720870870f62cedfddeb9f81b934c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3089512
Reviewed-by: Ryan Beltran <ryanbeltran@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
We keep a clone of the LLVM repository, which we create if it did not
already exist. This takes a while, so we inform the user. However, the
message did not specify where we are cloning to or why. This change
makes the message take the form:
Checking out LLVM to '<path>'
so that we can map between commit hashes and revision numbers.
This may take a while, but only has to be done once.
BUG=b:192699914
TEST=ran llvm_tools/get_llvm_hash.py with a few parameters
Change-Id: I86d83f03ab293c5cfb3014e80175c674740a2818
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3078689
Tested-by: Bob Haarman <inglorion@chromium.org>
Reviewed-by: Jordan R Abrahams <ajordanr@google.com>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
|
|
Update wrapper installation script now that we have
separate clang and gcc wrappers.
BUG=b:186803617
TEST=run install_compiler_wrapper.sh
Change-Id: I14ee2ffc6f74adb9699066a54dbead98e2f2e220
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3078693
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Auto-Submit: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Jian Cai <jiancai@google.com>
|
|
Update chromeos-kernel-3_18
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: Ia1b921900388cfa7bb21c30813356d7e367e8e0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3076780
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Auto-Submit: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Jian Cai <jiancai@google.com>
Commit-Queue: Jian Cai <jiancai@google.com>
|
|
Sourcing this properly from LLVM is awkward, since at the least, we'd
need to keep an LLVM git repo around. On top of that, we'd need to come
up with some way to pin this at a specific version (since the evolution
of LLVM ideally shouldn't impact the functionality of bits here).
Rather than dealing with all of that, let's just copy this from the
repo and declare victory. Changes should be super rare anyway. :)
BUG=chromium:194731505
TEST=./nightly_revert_checker_test.py
Change-Id: I6179cae57d01bee7cae7883c93f71cb9c2f1f3d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3068861
Reviewed-by: Bob Haarman <inglorion@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
This reuses existing perf reports to identify idle samples instead of
regenerating them.
BUG=b:194737325
TEST=Ran crosperf with cwp benchmarks.
Change-Id: Ib024addbcfb278815fa55dcab20c6d7db90b287a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3062781
Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Jian Cai <jiancai@google.com>
|
|
Do not add static-libgcc to compiler command line if user
is passing {shared|static}-libgcc.
BUG=b:187794119
TEST=CQ
Change-Id: Iecd969dd11632837013bea71df9547bd08bbf30c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3064572
Reviewed-by: George Burgess <gbiv@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
Auto-Submit: Manoj Gupta <manojgupta@chromium.org>
|
|
This appeases the "file needs a trailing newline" lint warning when
running `repo upload` with local changes created by
get_upstream_patch.py.
BUG=b:194873857
TEST=`repo upload` passed.
Change-Id: Icc4bf60009182290f2d0beb10f5ee7fefe14e044
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3068076
Reviewed-by: George Burgess <gbiv@chromium.org>
Tested-by: Jian Cai <jiancai@google.com>
|
|
At the request of gbiv@, I'm updating the yapf style guide to
pep8, as the chromium style apparently has very similar style
to pep8.
BUG=None
TEST=CQ
Change-Id: I965250cc7482aed4791a09391b37487bc00e618f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3068280
Reviewed-by: George Burgess <gbiv@chromium.org>
Tested-by: Jordan R Abrahams <ajordanr@google.com>
Commit-Queue: Jordan R Abrahams <ajordanr@google.com>
|
|
It seems that LLVM has an old precedent of `release/${version}`
branches, but has swapped to naming new branches
`upstream/release/${version}`. This includes a retroactive addition of
`upstream/release/${version}` for old versions, which makes the
`ValueError` here get raised. Prefer the newer, shinier names.
BUG=b:194731505
TEST=./git_llvm_rev_test.py
Change-Id: If170c004eae0edf1a69792207e5c681deb10e50b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3068860
Reviewed-by: Bob Haarman <inglorion@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
Right now Crosperf reports include samples from idle functions.
Filtering these samples from the reports allow users to have more
accurate evaluation of the performance impact of code changes as they
focuson the meaningful samples.
BUG=b:194737325
TEST=unit tests passed.
Change-Id: I22bc3c78999eec9a141440e92ce52457a4bfa0a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3054437
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Jian Cai <jiancai@google.com>
|
|
This fix the missing symbols in perf report due to the misplaced debug
information.
BUG=b:194540821
TEST=Ran crosperf and verified all the symbols are present in the perf
report.
Change-Id: Ifed66ac6073d175d99a71e64f5e89925fabdaa92
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3050514
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Jian Cai <jiancai@google.com>
|
|
Update compiler wrapper for migrating the wrappers from
gcc to llvm ebuild.
This assumes that clang wrappers now live in /usr/bin/
instead of /usr/x86-64-pc-linux-gnu/... and is no longer
co-located with gcc wrappers.
BUG=b:186803617
TEST=CQ, SDK tryjobs
Change-Id: I60082913dbf5a3c6ce992ea951955086b280af43
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3046721
Reviewed-by: George Burgess <gbiv@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
|
|
is changed"
This reverts commit a5725194cabd4244fd04c106c3a8d8b0d246b751.
Reason for revert: breaks llvm-next testing. b/194493350
Original change's description:
> [llvm_tools] automatically uprevs sys-devel/gcc whenever LLVM_NEXT is changed
>
> BUG=b:192996912
> TEST=update_chromeos_llvm_hash_unittest.py verified via CQ
>
> Change-Id: Id06f054fdc4400c9b9af48c5383172192cb9a8a3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3021576
> Tested-by: Christopher Di Bella <cjdb@google.com>
> Auto-Submit: Christopher Di Bella <cjdb@google.com>
> Reviewed-by: Luis Lozano <llozano@chromium.org>
> Commit-Queue: Christopher Di Bella <cjdb@google.com>
Bug: b:192996912, b:194493350
Change-Id: I3a8e70bc20f09d92d594c1821b90157b6b5aba18
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3048754
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
|
|
BUG=b:191618957
TEST=wrapper test
Change-Id: I4340173ae681a6c5f022a3b1f1e890d2c9ee8b99
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3036676
Commit-Queue: Luis Lozano <llozano@chromium.org>
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Auto-Submit: Luis Lozano <llozano@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
|
|
Update chromeos-kernel-3_18
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: I243691ed09c42b114c594eea0467fd1f94cf440b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3036204
Reviewed-by: Jordan R Abrahams <ajordanr@google.com>
Reviewed-by: Jian Cai <jiancai@google.com>
Commit-Queue: Bob Haarman <inglorion@chromium.org>
Tested-by: Bob Haarman <inglorion@chromium.org>
|
|
BUG=b:192996912
TEST=update_chromeos_llvm_hash_unittest.py verified via CQ
Change-Id: Id06f054fdc4400c9b9af48c5383172192cb9a8a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3021576
Tested-by: Christopher Di Bella <cjdb@google.com>
Auto-Submit: Christopher Di Bella <cjdb@google.com>
Reviewed-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Christopher Di Bella <cjdb@google.com>
|
|
This CL implements defaulting the output directory for bundle.py to the
location of compiler wrapper files in third_party/chromiumos-overlay.
This also prevents bundle.py from creating directories unless a new
--create flag is specified.
BUG=None
TEST=Manually tested
Change-Id: I64d055a73332d3faafad730beda30886212346ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/3016910
Commit-Queue: Ryan Beltran <ryanbeltran@chromium.org>
Tested-by: Ryan Beltran <ryanbeltran@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
Update chromeos-kernel-3_18
Update chromeos-kernel-4_4
Update chromeos-kernel-4_14
Update chromeos-kernel-4_19
Update chromeos-kernel-5_4
BUG=None
TEST=Verified in kernel-release-afdo-verify-orchestrator
Change-Id: I4091d87b7899ef75faa4054069b5c26dfb89f63e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2989634
Reviewed-by: Luis Lozano <llozano@chromium.org>
Tested-by: Luis Lozano <llozano@chromium.org>
Commit-Queue: Ryan Beltran <ryanbeltran@chromium.org>
|
|
This CL adds --rewrapper-path support to the compiler, as requested in
the linked bug. The use of this is mutually exclusive with that of
--gomacc-path.
We currently look for either a `--gomacc-path` flag or a `GOMACC_PATH`
env var to enable goma. If any rewrapper flag is specified, this
disables our checking of `GOMACC_PATH` for the purposes of mutual
exclusivity checking.
BUG=b:190741226
TEST=go test, a few manual invocations
Change-Id: I03dd2835a313806a9700c49c47c82fecf19a4b7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2956696
Reviewed-by: Ryan Beltran <ryanbeltran@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
This is intended to be no functional change. In most places, we use
"goma" as a way of saying "remote compilation;" this CL clarifies which
is which.
BUG=b:190741226
TEST=go test
Change-Id: Ia03c1a05486c907cd6f7bc33b59a56c98db5d527
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2956695
Reviewed-by: Ryan Beltran <ryanbeltran@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|