summaryrefslogtreecommitdiff
path: root/tcwg_bmk-build.sh
diff options
context:
space:
mode:
authorChristophe Lyon <christophe.lyon@linaro.org>2021-03-02 20:46:21 +0000
committerChristophe Lyon <christophe.lyon@linaro.org>2021-03-02 20:46:21 +0000
commite7cdaad318b4ef5f2760f0142a977488712192b2 (patch)
treedfa5569f52ccacc3058d5640c7c56d66c5ad8f9b /tcwg_bmk-build.sh
parent1360b58f6bed64d011ec9b068c02cf2b5ad6c37a (diff)
tcwg_bmk-build.sh: Use rsync to access the toolchain when target is stm32
When running benchmarks on stm32, it's easier to rsync the toolchain towards tcwg-bmk-stm32-01 (slave to which the stm32 board is attached) rather than involving the tricky process of rsync-ing the benchmark sources towards the builder and remote compile, like we do for Spec. Change-Id: I2c87bcc7fbc80ba9d75d5c88a33a15f8e928b5bc
Diffstat (limited to 'tcwg_bmk-build.sh')
-rwxr-xr-xtcwg_bmk-build.sh9
1 files changed, 8 insertions, 1 deletions
diff --git a/tcwg_bmk-build.sh b/tcwg_bmk-build.sh
index 71e987db..b2c833ed 100755
--- a/tcwg_bmk-build.sh
+++ b/tcwg_bmk-build.sh
@@ -246,6 +246,13 @@ benchmark ()
esac
local results_id="$results_top/${rr[ci_project]}/${rr[mode]}-${rr[ci_config]}/@build_num@"
+ # When running benchmarks on stm32, we prefer to rsync the
+ # toolchain towards tcwg-bmk-stm32-01.
+ case "$hw" in
+ stm32) toolchain_proto=rsync ;;
+ *) toolchain_proto=ssh ;;
+ esac
+
# shellcheck disable=SC2154
remote_exec "ci.linaro.org:2222::-l $USER@linaro.org" \
build tcwg-benchmark-$hw -w \
@@ -255,7 +262,7 @@ benchmark ()
-p testmode=benchmark \
-p displaytag="${rr[ci_project]}/${rr[mode]}-${rr[ci_config]}" \
-p ignore_errors=true \
- -p toolchain_url=ssh://$ssh_host:$ssh_port:$cc \
+ -p toolchain_url=$toolchain_proto://$ssh_host:$ssh_port:$cc \
-p toolchain_type=$toolchain \
-p sysroot="$sysroot" \
-p results_id="$results_id" \