From 6f022a7416870326951b256ba67b324390d3df37 Mon Sep 17 00:00:00 2001 From: David Spickett Date: Mon, 18 May 2020 14:01:40 +0100 Subject: tcwg_bmk-build.sh: Always write benchmark results_id file Before it was only written when the job failed. (though the build number was in the log if you looked hard enough) This can be used to go from run_step failing, to the log of the actual benchmark. Change-Id: I8189518f948f9ac76d090ff635209a5e69762a98 --- tcwg_bmk-build.sh | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/tcwg_bmk-build.sh b/tcwg_bmk-build.sh index 39dc474d..b743555c 100755 --- a/tcwg_bmk-build.sh +++ b/tcwg_bmk-build.sh @@ -248,9 +248,16 @@ benchmark () # to check whether benchmarking has finished, and, if not, continue # to watch its output. build_status=$(tail -n 1 $run_step_artifacts/benchmark.log) + local build_ret case "$build_status" in - "Finished: SUCCESS") break ;; - "Finished: "*) return 1 ;; + "Finished: SUCCESS") + build_ret=0 + break + ;; + "Finished: "*) + build_ret=1 + break + ;; esac # Sleep a little to avoid flooding ci.linaro.org on transient ssh @@ -261,6 +268,8 @@ benchmark () echo "$results_id" | sed -e "s/@build_num@/$build_num/g" \ > "$results_id_file" ) + + return $build_ret } # Compare results between $1 and $2 and generate results-compare.csv -- cgit v1.2.3