Age | Commit message (Collapse) | Author |
|
Change-Id: Ic621c2a683c56267855bdec9706a87c280964b52
|
|
Change-Id: I6cb610ee01e9b592971dae36e343aec7d6350e47
|
|
Change-Id: Id741296cb5d7f68a21a3e83a5d0dcca04f97300c
|
|
... use $boardname instead.
Change-Id: Iddb92273402d03267e45edf16577ca66b447b10d
|
|
Change-Id: I11adaab039ae4abf593cfaa72253a8c48d306cd5
|
|
Change-Id: I3e3d42c4777528904a1c502bfb479fc466f9e261
|
|
Change-Id: I759fdf3e13c5b83a3ee68f1e9ccbd781a816803f
|
|
Change-Id: I084c675ed5c5cfe9d7a0a6e8cef710406d7c94f8
|
|
Change-Id: I3c1d7ea9907ffc243ae71ffa2aac4476458ff147
|
|
Change-Id: I0408d481d933372d7511ae10e2e0c8c1ef5bac4c
|
|
... to support tcwg-sq-01 and -02 boards.
Change-Id: Ifa7b49ad8da5fb537de4be312b08a276ae0861ad
|
|
Change-Id: I50adad4a8fc28f63bdcab9fd55eb16e31607c2f8
|
|
Change-Id: Ibbfb9ccd93e1cd93a08875e6ea4997c93d6e1473
|
|
Change-Id: I0355ac53de92eb7a25d711d59e295ae46baf892d
|
|
Change-Id: I711c726552dd0b96bb3790dd9d6114d3cedb289f
|
|
This is to, hopefully, recover from filesystem failures like below:
00:02:35.206 + ssh tcwg-tk1-06.tcwglab sudo /sbin/reboot
00:02:35.306 Failed to start reboot.target: Unit reboot.target is not loaded properly: Input/output error.
00:02:35.307 See system logs and 'systemctl status reboot.target' for details.
00:02:35.308 Failed to open /dev/initctl: No such device or address
00:02:35.308 Failed to talk to init daemon.
...
00:03:05.323 + wait_for_ssh_server tcwg-tk1-06.tcwglab 22 100
...
00:03:05.346 + rsync -az --delete bmk-scripts/ tcwg-tk1-06.tcwglab:bmk-scripts/
00:03:05.514 rsync: failed to set times on "/home/tcwg-benchmark/bmk-scripts/.git": Read-only file system (30)
Change-Id: I9c1b50d18034a7c6317505f0e770791bc178e8b7
|
|
... and $EXTERNAL_FAIL. This allows us to distinguish between
regressions that we should bisect and infra problems that we
should skip bisects for.
Change-Id: I8f3b82c86d95e27351b01a2b3d2467b8e15b309e
|
|
... container. So that prepare-board.sh/benchmark.sh script has a chance
to fix broken docker daemon.
Change-Id: I5e20606141b91987fe99f7369494d0b10b06da56
|
|
Change-Id: I8c6ec7118f9015fa3ad3ea8c344fb66b5bf9a357
|
|
Change-Id: I49685c1938c44548f88928c7afa455a863af8076
|
|
Change-Id: I6530286516fc131980e4379399ca0fff00883f8f
|
|
Also update the sanity check
script to include .job files.
Change-Id: Ibf72d9ff346ff7b012d4e282a6ac8f3b7e73590d
|
|
First round of low hanging fruit
from the files with the fewest
warnings.
Change-Id: I60ad57b5bfb2f0be9bb6506252c820f44d055200
|
|
* Dedupe getting hostname for ssh
toolchain URLs
* Check toolchain type earlier
* Error if SSH doesn't respond after reboot
(and change the other uses of
wait_for_ssh_server to follow the same format)
Change-Id: Ib7823e5a83500e0d95912ef0d3ba993051a67533
|
|
... instead of "tcwg-tested" due to
https://projects.linaro.org/browse/LSS-1153 , which causes
tcwg-tested images to not being updated.
Change-Id: I2222b87892b029b23eb1baeb28747b148addb345
|
|
... job into tcwg-benchmark-tk1 and tcwg-benchmark-tx1.
Change-Id: Ieccafcaa47fa522cc00d6ffd69fcc3494eb5a120
|
|
Change-Id: I2dda965799f91f6a94760e99fefc76ecb2749a1e
|
|
Change-Id: I7adcb1f58bcdd4f6f5f74d3e790cbb249bba943c
|
|
Change-Id: I798c651d7a02c3f0a5ace45e125e3552836fa71a
|
|
... by using remote_exec, which quotes parameters appropriately.
Change-Id: Ic62a08fab198b9293873541aa49a90c9e402c9a9
|
|
We have configuration steps that are needed to be run
on the host board (e.g., stopping/starting services) and inside
the container (e.g., starting/stopping perf workaround).
Container can't stop services on the main machine (unless we
proxy systemd interface somehow), and perf workaround is best
to be started using the version of perf that benchmarking uses.
Change-Id: I135060d043eb03946aef3d02e333df5902d1c8b7
|
|
Change-Id: I9d082ddbb9caf2fa498c05220153184f93fe4c17
|
|
Don't forget to cleanup "build" container as well as "run" container.
Change-Id: I836f418ba22e5b4aab16867d0745a4d44107708a
|
|
Don't tie benchmarking and build container images.
Change-Id: Id034072f469fa4fc50a429a2afbf560dd51a0a93
|
|
... to enable removal of stale/aborted benchmarking containers via
$WORKSPACE/.lock cleanup.
Stale benchmarking containers are dangerous due to perf workaround
running inside, which steals samples from the "measuring" perf.
Change-Id: I54dfbb42e5d04ff49c9bfb591df681cf16c5b781
|
|
Change-Id: If6f5d03352dd72d4a9e7345950efd65ae7f83eb0
|
|
This creates a new task ('bench') and starts a docker container to run
the benchmarks in. It uses the same image as the 'build' task.
Switching between aarch64 and aarch32 benchmarking breaks unless force
install is requested because we only keep one version of the spec tools
on the board. This will be fixed in a subsequent patch to bmk-scripts.
Change-Id: Ie98cdf47aa3ed456e6349bac40d88bd7acaa7acd
|
|
... by adding ability to set custom linking flags.
See https://projects.linaro.org/browse/LLVM-557 .
Clang's driver needs fixing to avoid passing -Os/-Oz to the linker.
Change-Id: Id1858483f18babd95cd79c645479cdc6a2e378f0
|
|
This patch updates tcwg_bmk-build.sh from the original copy of
tcwg_kernel-build.sh, and adds a couple minor changes to docker-run.sh
and tcwg-benchmark-results.sh.
tcwg-benchmark*: Switch results server to bkp-01.tcwglab
tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's build
round-robin.sh: Build LLVMgold.so plugin in build_llvm() for LTO
Change-Id: Ibde7a9d004c8b3328cdd36333c14574934b1eeab
|
|
... to remove old results and avoid filling up the disk.
Change-Id: Ife87756fc92f48717baa0f84c7c3fe16b49b1899
|
|
We [ab]used build_container_exec to ssh the target board to get
most recent ssh configuration. We have since started to require
local ssh access to work as well (e.g., for reboot functionality),
and implemented automatic updates of tcwg-buildslave and
tcwg-benchmark /home files.
Also, don't use ssh multiplexing (-Snone) to reliably forward
ssh agent to the benchmarking board. We have seen strange
ssh-agent failures over shared connections.
Change-Id: Iab09821272aa91f8a80b0e1b8fc5a9dd1a6bd3fb
|
|
We just need to keep this parameter if present, and pass it to run.sh
unchanged. Just take care that the path component in a ssh://
toolchain is always the last one.
Change-Id: I581af110e4df06adce5fcdfb3ae722ea74fc6451
|
|
Change-Id: I4217c5c3f2b677f00a8bb43bb56b9044aa1b83ba
|
|
Change-Id: Iab7b696ba0972db8e2362aa0896af9a35e179839
|
|
Make sure we could determine it.
Change-Id: I5ac789d0ec8eb78ea016e83751ed132d8900cc92
|
|
Change-Id: I8397a8bcbeda5892d314f0675cc9be0c428cd214
|
|
build container.
Change-Id: I4d7400dc9c138e1e7a5339dadfafd6aa4aaf9a26
|
|
If toolchain_url is of ssh:// type, do not create a remote build
container, just use the ssh connexion as provided.
Change-Id: Id93be63fd61a0d99d433d7b6ebb65f0e1c2473f8
|
|
Replace ${var:-default} with ${var-default}.
I learned something new about shell scripting today. From bash manual:
===
When not performing substring expansion, using the form described
below (e.g., ‘:-’), Bash tests for a parameter that is unset or null.
Omitting the colon results in a test only for a parameter that is
unset. Put another way, if the colon is included, the operator tests
for both parameter’s existence and that its value is not null; if
the colon is omitted, the operator tests only for existence.
===
The immediate problem I need to fix is handling of
host_aarchXX_excludecheck and host_x86_64_excludecheck parameters
in tcwg-buildfarm.sh. With ":-" syntax the empty ("null") values are
replaced by defaults, causing GCC testsuite to be ignored on aarchXX
hosts when "--host_aarchXX_excludecheck ''" is given.
There happens to be a single usage ":-" in ${rw:-rw} in
start-container-qemu.sh, where ":-" is actually needed.
Change-Id: Ibc8e070b698e1c76e2161eb65d40639b8cdec1f3
|
|
Change-Id: I0abd9f0c7ec0da98990459cf175eb4e076bdab8d
|