Age | Commit message (Collapse) | Author |
|
Update chromeos-kernel-4_4 from R81-12828.0-1579516426 to R81-12847.0-1580121216
Change-Id: I61a4b5bb2d01211827c4b70a818d884f77763082
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2024013
|
|
Update chromeos-kernel-3_18 from R81-12828.0-1579516702 to R81-12847.0-1580121376
Change-Id: Ifd925b3a8159dc2382480bcd8c5ff430d6ffa529
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2023782
|
|
`requests` is an artifact of an old way of doing things, and breaks
things on Android bots. Best to just remove it.
This also fixes other misc lints in that file
BUG=b:147699825
TEST=unittests
Change-Id: I3f465f9a129679b104e328ab8307298af1df651b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2023775
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Pirama Arumuga Nainar <pirama@google.com>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
The resource dir value returned by calling clang has a new line
character. This breaks running clang with
"-Xclang-path=/path/to/<clang_dir>" functionality as the resource
directory with this new line does not exist.
BUG=chromium:1044790
TEST=compilation with "-Xclang-path=/path/to/<clang_dir>" works.
Change-Id: I0ef31108719aed02a433aff3e751e961892dd15a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2017844
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
This patch removes afe locking mode for crosperf, since:
1) All lab machines has been migrated to skylab.
2) Interaction with afe depends on python 2 code in autotest.
BUG=chromium:1044764
TEST=Passed unittest and simple experiment run.
Change-Id: Ie0a250548d739f32bbc08619f637380104df6c28
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2016008
Commit-Queue: Zhizhou Yang <zhizhouy@google.com>
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
Exporting BISECT_STAGE to POPULATE_GOOD currently makes the wrapper fail
to build any files with the error message of "ModuleNotFoundError: No
module named 'bisect_driver'". This patch fixes the issue by adding
search path for bisect_driver.py explicitly.
BUG=chromium:1042452
TEST=verified locally.
Change-Id: I7c73459b377d9011c7087a9e241db378ffb216e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2003947
Tested-by: Jian Cai <jiancai@google.com>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
Update chromeos-kernel-4_4 from R81-12814.0-1578911615 to R81-12828.0-1579516426
Change-Id: I520e115bf5ebc19f71b21cfc66d887289df732cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2013699
|
|
Update chromeos-kernel-3_18 from R81-12814.0-1578912053 to R81-12828.0-1579516702
Change-Id: Ib1a2799a3da46e6f695335c6a1d00d2142c4297c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2011332
|
|
BUG=chromium:1042953
TEST=verified locally.
Change-Id: I1a452c2756491e69121a161a32ab007c4e79629d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2006728
Reviewed-by: George Burgess <gbiv@chromium.org>
Tested-by: Jian Cai <jiancai@google.com>
|
|
Fix unused-argument complaints in unit tests.
BUG=chromium:1042953
TEST=verified locally.
Change-Id: I7037fc10f8160a5f1f8929a3256e91255dd125ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2006330
Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Jian Cai <jiancai@google.com>
|
|
This is the first step of python 3 migration for crosperf
TEST=Passed presubmit for all .py files in crosperf
BUG=chromium:1011676
Change-Id: I615d0323c81ba688c8ce2aa0cac307035d0b882b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/2001696
Commit-Queue: Zhizhou Yang <zhizhouy@google.com>
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
Update chromeos-kernel-4_4 from R81-12739.12-1578524221 to R81-12814.0-1578911615
Change-Id: Idf3377bef43b5e6bbb1e0cecdee6fa86efc4131b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1999556
|
|
Update chromeos-kernel-3_18 from R81-12739.12-1578524538 to R81-12814.0-1578912053
Change-Id: Icfdc2be38124baa29c319e6bcaa94cbd2e9a7c31
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1998600
|
|
As for goldmont, tremont is too new a march for the version of gcc that
is used. Thus, the flags processor for gcc should translate that request
back to silvermont. This is needed to use the new march with clang.
BUG=b:147468258
TEST=go test
Change-Id: Idc6b04f40fc7f0a663b1ff8ff57df109a2193dad
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1995313
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Justin TerAvest <teravest@chromium.org>
Commit-Queue: Justin TerAvest <teravest@chromium.org>
Tested-by: Justin TerAvest <teravest@chromium.org>
|
|
My local llvm-project-copy was out-of-date. It's nice if we can
automatically handle that.
This also fixes lints and such that weren't able to fire when this was
originally landed.
BUG=chromium:1041016
TEST=Wiped out my LLVM tree; it synced without issue. Tried syncing with
a timedelta of seconds=2; everything WAI.
Change-Id: I4a4811bb1500db0b00c924eec0be12dc57499fc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1995316
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
llvm grew a relatively large merge commit recently, which broke this
script noticeably.
There's analysis of why this happened in the bug. tl;dr is that
`rev-parse ${sha}~${N}` and `rev-list --count` don't do the same thing
without extra flags.
BUG=chromium:1041016
TEST=Unit tests. A few random runs in my LLVM tree.
Change-Id: I393d1ada842b5f19846d961b403641bc958b191f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1995315
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: George Burgess <gbiv@chromium.org>
|
|
Update chromeos-kernel-4_4 from R81-12739.12-1578306749 to R81-12739.12-1578524221
Change-Id: I7237964ac964ea3208a7538accbda8b7c5b54932
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1995000
|
|
After we migrate cros_utils code to python 3 style, one argument that is
called by buildbot_test_llvm has changed. 'async' becomes a keyword in
python 3 and cannot be used. This patch fixes it.
TEST=Script launched correctly.
BUG=chromium:1011676
Change-Id: I520a8034d4dc21425c52acc7a2b7efb715927e05
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1992704
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Reviewed-by: Denis Nikitin <denik@chromium.org>
Commit-Queue: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
|
|
Update chromeos-kernel-3_18 from R81-12739.12-1578306983 to R81-12739.12-1578524538
Change-Id: I0c28856f7dec18d917f1292f286a284ac5114dd2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1994462
|
|
Update chromeos-kernel-3_14 from R81-12607.58-1577702661 to R81-12607.58-1578524353
Change-Id: Ic8d9cf96e8a762bc30120f8499501d8c39790f85
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1992855
|
|
This patch fixes all presubmit checks in cros_utils and migrated it from
python2 to python3.
TEST=Passed all unittests and presubmit checks.
BUG=chromium:1011676
Change-Id: I3a7097d6570fb2cb4e5dcdd5ae22f30c5c5762e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1981087
Commit-Queue: Zhizhou Yang <zhizhouy@google.com>
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
Update chromeos-kernel-4_4 from R81-12756.0-1577702613 to R81-12739.12-1578306749
Change-Id: I362a2bb0371752ac85ce8c387771427707ed475d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1989262
|
|
Update chromeos-kernel-3_18 from R81-12739.12-1577702242 to R81-12739.12-1578306983
Change-Id: I3fee5e7f0e4c439381958c9e4f4835ad5f3f8845
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1988935
|
|
Update chromeos-kernel-4_4 from R81-12756.0-1577097242 to R81-12756.0-1577702613
Change-Id: I627a471088a51d0a06a935bb8febe1fed22ac85b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1984860
|
|
Update chromeos-kernel-3_18 from R81-12739.12-1577097165 to R81-12739.12-1577702242
Change-Id: Ibd487e9f2f26de31dad9e5ee0f4a01eb0d78e2a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1984432
|
|
Update chromeos-kernel-3_14 from R81-12607.58-1577097920 to R81-12607.58-1577702661
Change-Id: Iad97870d767846d8e580c2d1003579903189344c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1984335
|
|
Update chromeos-kernel-4_4 from R81-12750.0-1576492613 to R81-12756.0-1577097242
Change-Id: I1a656a93f07f6e9949a0c7deb12feb278e5e898b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1981819
|
|
Update chromeos-kernel-3_18 from R81-12739.4-1576492394 to R81-12739.12-1577097165
Change-Id: Ieb40afb8164ccbf99c94d9d59f0f55e0ba5bfac5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1981584
|
|
Update chromeos-kernel-3_14 from R81-12607.56-1576493276 to R81-12607.58-1577097920
Change-Id: I4beebf569b74550882ae8e6881926a0ee7992e8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1981571
|
|
Update chromeos-kernel-3_18 from R80-12607.47-1575888165 to R81-12739.4-1576492394
Change-Id: I04648948cb4d26bc6879e098e2c5b4b537323a2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1972409
|
|
Update chromeos-kernel-4_4 from R80-12714.0-1575887745 to R81-12750.0-1576492613
Change-Id: I59c80dd5b407724de1c6ae2835123fe5c909a35a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1970153
|
|
Update chromeos-kernel-3_14 from R80-12607.47-1575888027 to R81-12607.56-1576493276
Change-Id: Icdd4ae26897b7db9ffa485466d7e0e30b072a302
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1969262
|
|
Current command generated from suite_runner for telemetry_Crosperf run
is not correct, and this patch will fix it. Also added an unittest to
verify it in the future.
It is unfortunate that we currently still cannot run test with args
successfully in skylab, but according to the args passed to skylab, this
change should work.
TEST=Checked command line to launch skylab create-test.
BUG=None
Change-Id: I05f0f4c60e04d19e2a2637192023829d4dd9f48b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1963355
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Zhizhou Yang <zhizhouy@google.com>
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
|
|
Use '--intel_pstate=no_hwp', rather than '--no_hwp' (not a valid
argument), for launching nightly performance Crosperf tests.
BUG=None
TEST=Launched crosperf manually on chrotomation2 with this and it
worked.
Change-Id: Ia6474e3fb99bd30c79e15465dff0b54903e2a6f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1965433
Reviewed-by: Tiancong Wang <tcwang@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
|
|
We should not image DUT with certain image when the test is going to be
launched via 'skylab create-test'. This is because the DUT may be
occupied by other tasks before Crosperf acutally get it assigned, and
the first step after the test starts is to flash image.
This patch is a temproray solution to ensure no bad behavior happens on
the DUT before testing.
TEST=Tested wth skylab run, w/o caching.
BUG=chromium:984790
Change-Id: Ie2f439d5777813905bdca5f4a2d1e401df2dc83e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1952172
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Reviewed-by: Caroline Tice <cmtice@chromium.org>
Commit-Queue: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
|
|
This is a patch working together with crrev.com/c/1949606 to migrate
device setup functions from suite_runner to autotest telmetry_Crosperf.
In this patch, we modified the logic of different suite types along with
skylab mode for suite_runner.
In result_cache, we handle the wait time log file to accumulate cool
down time per machine.
We also move intel_pstate kernel updating code into SetupDevice() since
it doesn't increase overhead by checking every iteration.
TEST=Passed all unittests; tested with different benchmark modes (Note
that currently skylab server tests cannot be tested because of
regression: crbug.com/984103).
BUG=chromium:1020655
Cq-Depend: chromium:1949606
Change-Id: If8e5099d096d2568d4f54584a8fcfd3c0f99c8f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1949626
Reviewed-by: George Burgess <gbiv@chromium.org>
Reviewed-by: Denis Nikitin <denik@chromium.org>
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
Commit-Queue: Denis Nikitin <denik@chromium.org>
|
|
Nothing reads this file anymore.
BUG=chromium:1025955
TEST=CQ passes
Change-Id: Ib6443aa3c4395cf5198dad75f0bfda7ea907fd63
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1961388
Reviewed-by: Caroline Tice <cmtice@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
|
|
Update chromeos-kernel-3_18 from R80-12607.34-1575282780 to R80-12607.47-1575888165
Change-Id: I95c903dfeccf4338d2fffab427e8c65d3e2f5f81
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1960947
|
|
We should mention git hashes in the CLs automatically created for LLVM
roll now that the hashes become the only revision numbers LLVM uses.
BUG=chromium:1027950
TEST=local tests.
Change-Id: Iaec59599d4fa0d133e09d2a31db45c777a2d1e60
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1959439
Commit-Queue: Jian Cai <jiancai@google.com>
Tested-by: Jian Cai <jiancai@google.com>
Reviewed-by: George Burgess <gbiv@chromium.org>
|
|
Update chromeos-kernel-3_14 from R80-12607.34-1575283400 to R80-12607.47-1575888027
Change-Id: I5280f8bd0a034fbdf3e0f6f052a3b0e31137ee89
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1960199
|
|
Update chromeos-kernel-4_4 from R80-12672.0-1575282851 to R80-12714.0-1575887745
Change-Id: I0440db51f686166fe20cee15d52aac3180f6e84a
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1959818
|
|
BUG=None
TEST=./copy_helpers_to_chromiumos_overlay.py
Change-Id: I8296968ac8e51b48c84c877e0f8610832721bcc2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1957896
Tested-by: George Burgess <gbiv@chromium.org>
Auto-Submit: George Burgess <gbiv@chromium.org>
Reviewed-by: Caroline Tice <cmtice@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
|
|
Currently there is a trailing newline no the git has that is
causing git rev-parse to fail. This CL removes the trailing newline.
BUG=None
TEST=None
Change-Id: I509871fda6bc7ec77bf088d54490b68d3b58e268
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1957891
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Caroline Tice <cmtice@chromium.org>
Tested-by: Caroline Tice <cmtice@chromium.org>
|
|
Sync python scripts from sys-devel/llvm/files/patch_manager that fixed
broken LLVM roll builders.
BUG=chromium:1027950
TEST=local builds.
Change-Id: I0f1c7147e937d59dfe859d36aa8cfcfcbfd1fdb9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1949693
Reviewed-by: George Burgess <gbiv@chromium.org>
Commit-Queue: Jian Cai <jiancai@google.com>
Tested-by: Jian Cai <jiancai@google.com>
|
|
Rendering.desktop benchmark which was added into crosperf does not
return results in avg_surface_fps field. Until recently it worked fine.
There is an alternative field in histograms.json "exp_avg_surface_fps"
holding the data.
Add exp_avg_surface_fps in default-telemetry-results.json to filter-in
the benchmark field in crosperf results.
BUG=chromium:1030475
TEST=crosperf with rendering.desktop returns data on chell and lulu
Change-Id: Ia1d25f7f1894ca559f1e14e032fcf274dc4df49d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1951336
Reviewed-by: George Burgess <gbiv@chromium.org>
Tested-by: Denis Nikitin <denik@chromium.org>
|
|
This patch moves enable_aslr and turbostat into dut_config dictionary,
since they are all device setup steps, and it make code cleaner and
easier to migrate to telemetry_Crosperf.
TEST=Passed unittests.
BUG=chromium:1020655
Change-Id: I29a649e76591e206efc19bb2b8a8df9aead16575
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1947903
Reviewed-by: Denis Nikitin <denik@chromium.org>
Commit-Queue: Zhizhou Yang <zhizhouy@google.com>
Tested-by: Zhizhou Yang <zhizhouy@google.com>
Auto-Submit: Zhizhou Yang <zhizhouy@google.com>
|
|
Update chromeos-kernel-4_4 from R80-12672.0-1574678359 to R80-12672.0-1575282851
Change-Id: I13cfd049f6e873a3bd8458c6a5b3bf43eeee5a00
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1947905
|
|
There was a bug when crosperf failed due to StopUI failure.
This happened when in a preceding run crosperf exits with an exception
in DeviceSetup (for example Keyboard interrupt) and fails to call
StartUI.
Current change fixes this problem and includes a unittest case testing
the exception case.
BUG=None
TEST=unittest and HW test on DUT with stopped ui pass
Change-Id: Id6c69aebefe21b12ec7ee3a7c7f9dff92d143908
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1941036
Commit-Queue: Denis Nikitin <denik@chromium.org>
Tested-by: Denis Nikitin <denik@chromium.org>
Reviewed-by: Zhizhou Yang <zhizhouy@google.com>
|
|
Update chromeos-kernel-3_18 from R80-12607.34-1574677964 to R80-12607.34-1575282780
Change-Id: I51d1072813365866ef58e8106b48f6f4fe482e89
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1946757
|
|
Update chromeos-kernel-3_14 from R80-12607.34-1574678010 to R80-12607.34-1575283400
Change-Id: I1c97b39f32d73668e43be01e22ae9140e6f55044
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/toolchain-utils/+/1945800
|