Age | Commit message (Collapse) | Author |
|
Change-Id: I7a4246770fac9e1dfdee54fd6e7494881af83929
|
|
Change-Id: If634e49be6d250f6ab551a3139db8c21e2edcb75
|
|
forceinstall options
Change-Id: I2cc0ba3b45ff1251004205967fc4fa6e19f96bf7
|
|
Change-Id: I167646dfdc83c8256f85ebd7b7a9903b12517bef
|
|
Change-Id: Ie26da7540313c4caa2ee67baf0ee55c44b9f3433
|
|
Change-Id: I1080ecf5a2718b0052cd3d87c8b2f1acb312646c
|
|
Change-Id: I6862dfa8fe2afbce11a454835046a166ce022539
|
|
Change-Id: Ic7dc1af5b5722c92430b2ce56bed64c3e1ead227
|
|
|
|
Change-Id: Ied62dcd9c470afbec7beee5763e9d57c0c888cc2
|
|
Otherwise we try to create two containers with the same name (one for
build, and one for benchmarking).
Change-Id: If8492174ce31911f4ee0cdc13ba0c2efc863493c
|
|
Change-Id: I10be7a75d91f2227d5f2735f46d2b832bf85dc39
|
|
Change-Id: Ie353ffbd8129baac8fc99f05925c52b97d81dfde
|
|
To run coremark on stm32 board
Change-Id: I1cd35a94af442ca12f53112e5fa8847b6bed69a1
|
|
Change-Id: I73e2ef1da8cb474b18a366ecccae09ab83185480
|
|
Sigh, the previous patch used a syntax that applies only with using an
rsync daemon (with rsync: protocol).
Let's use -e 'ssh -p 22', like we do in other scripts.
Change-Id: I41d3cb7ff843abcc56a94775e2fd04c5f317f7fa
|
|
Adding "-p 22" does not work for rsync, which expects the port number
as a ":port" suffix for the host specification.
Change-Id: I41dbfbe11f73fd02386f90a0266488557a0009c7
|
|
Our default ssh config points to the host container where the
directory containing the binary tarballs is not mapped.
Use port 22 to upload them to the right location.
Change-Id: I5f18365f9d36541e3133ca81ed9ac2ac560bef30
|
|
Change-Id: I9fd245d77848f0d8d1d2117ed117b1f17e2bcdd5
|
|
Tcwg-benchmark-* jobs fail only due to infrastructure reasons.
Benchmark build and run failures are assigned special 99..99 and
88..88 metrics, but the jenkins build succeed.
Change-Id: I71639b6d4e1fd2a139390884c0d1eae0bb89a95d
|
|
Change-Id: I8c6ec7118f9015fa3ad3ea8c344fb66b5bf9a357
|
|
... which is represented by tcwg-benchmark-* build returning UNSTABLE
result.
Change-Id: Ifa8be8e601ef93412a3a62d9bed4a078fe38fa49
|
|
They are based on GCC's compare_tests but support a list of unstable
tests.
Change-Id: Icc582846d2cdd5df895cad373e3021fc7e154fbd
|
|
Don't expect ${c}_url defined when ${c}_branch is "baseline".
Change-Id: I436efd471dd55655ea9a125194823ed084552ecc
|
|
... which are referenced in base-artifacts repo.
This problem occurred when bkp-01.tcwglab, where we store benchmarking
results, ran out of disk space, so tcwg-benchmark-* jobs could not
upload their results. This didn't stop tcwg_bmk-build.sh to treat
this failure as regressions in various configurations, which were
then bisected down to the first commit. At that point baselines for
individual configurations were reset to the new failing state, and
references to the missing results were committed to base-artifacts repo.
We will fix this problem in several ways:
1. We have added tcwg-cleanup-stale-results.sh to parse base-artifacts
repo and delete results with no references from that repo (thus
preventing bkp-01.tcwglab from running out of disk space).
2. We are adding this workaround to purge broken entries from
base-artifacts repo.
3. We will commit .csv summary of results into base-artifacts.git so that
we won't need to rely on on-the-side storage of perf.data files.
Change-Id: I922df040292c1686f4461052d21bdeb98bea0b03
|
|
Change-Id: Iad5af1671239484b5a55830c75c23a8158d56252
|
|
Change-Id: I6e32f290ba92449905ca0c215ec13d0384ada938
|
|
Change-Id: Ibb21daee5883fade944073ef4cdb1d57ba905548
|
|
Change-Id: Ic648660f11602ebf82a34bd95469ba1018592287
|
|
Change-Id: I758566e05736de9c62ba8431843cb8c1c482b2d3
|
|
value
This is currently either build, bench or test.
Change-Id: I96fa7adad47e0bb8d95668462218fb21d08a2cd7
|
|
Change-Id: I4a6ce34a182245a77d5bb3e7ff59ac9667906430
|
|
Change-Id: I6735863b1937995e6e4883e0a811376222219bf4
|
|
See https://reviews.llvm.org/D80573
Change-Id: I6deee117fab24fcf91a9e283fec3898124accc9b
|
|
We're doing this because our .ssh/config connects to the host container
on dev-01 by default, and that doesn't have the upload directory mapped.
Change-Id: I80305eb168abd62eab95ce6c627178593a52a905
|
|
Change-Id: Iffa2dff5d9a937c94e9c69a4102c4739788ddefb
|
|
Change-Id: I472bf099af6d2ab6fb9dbb70c939634aaefafd48
|
|
... replace them with $bad_url.
Change-Id: I73224638e852367ed8c42a178f36e9f7bf6c401e
|
|
Change-Id: Id9495fa4785702f155bc845f4db1f8b7691e9a48
|
|
... when not using special "baseline" branch specifier.
Change-Id: If3aabeb1a2729b8d270d842fdd0ad5809ebc990d
|
|
Change-Id: Ide6dbb22152a5096ba21667f497f2571384579de
|
|
Change-Id: I79dc695cc2d4955516fc2ab55dfed031501d0a6b
|
|
... while keeping general logic the same. This approach sanity
checks that 2 configurations of cflags in *-vs-* configurations
are using the same mode.
To use different arm/thumb modes in *-vs-* configurations we would
need to build GCC and Glibc 2 times, which we could do, if required.
Change-Id: I3d9e6152b8b01f561e7e60557ccc680e99728103
|
|
Make "build_abe FOO" build FOO and make "build_abe check_FOO" run
FOO's testsuites. This also makes tcwg_gnu's bisections more
efficient, since we will ignore FOO's build problems in "check"
configurations.
Change-Id: I71c644e801828b94d880bed7fe440e4db3ffb40b
|
|
Don't bisect benchmark build/run failures in *-vs-*
configurations. These failures will also appear in non-vs
configurations, and will be bisected more efficiently.
Change-Id: Iad4a70a9b13e5509ff95e8dabde942a55f5c10b9
|
|
Remote_exec can exit before tcwg-benchmark-$hw job finishes,
and that's the reason why we loop until we see "Finished: "
on the job's console log.
Change-Id: Ib579a48e6a1e1f20d9f6d748efcf693df27d5c20
|
|
Right now when bootstrap fails we get score "0" from reset_artifacts,
and when bootstrap succeeds, but tests fail, we get same "0" from
"build_abe bootstrap". This makes us ignore bootstrap failures.
Fix by assigning reset_artifacts "-1" score.
Change-Id: I021c7f2c987634cde0a8052191955ac7c8a05f2e
|
|
... to tcwg-amp-03. This reduces load of linaro-armv8-01.
Change-Id: Ie742cd2af0dc4db70744a2bb91e2025b9a8b5ebe
|
|
Pass same fake git URL to abe in both build and check steps.
Before this patch we missed ".git" in the check step, which
caused ABE to try rebuild the component.
Change-Id: I0912854876b0054f413d168bd9152a2f530047a0
|
|
Move aarch64 full and global-isel bots to tcwg-amp-03 and armhf full
and global-isel bots to tcwg-amp-04.
Change-Id: Ie1192c3c908a540cb54494ad54ba90a6dad9a507
|