summaryrefslogtreecommitdiff
path: root/tcwg_bmk-build.sh
diff options
context:
space:
mode:
authorLaurent Alfonsi <laurent.alfonsi@linaro.org>2023-10-04 12:12:10 +0200
committerLaurent Alfonsi <laurent.alfonsi@linaro.org>2023-10-15 13:52:31 +0000
commitd10ab61e44bba4a7799ab820b71a14dbbdfcc388 (patch)
tree9ec1fd54b8c63fa617f330fbde7995793c2596f3 /tcwg_bmk-build.sh
parentd39b70ee3ca96abf3454eacd0a60e13662feb2d8 (diff)
round-robin.sh, tcwg_bmk-build.sh: run UNSTABLE for regressions to a negative score.
When encountering a score-based regression, leading to a negative score, we consider it as an EXTERNAL_FAIL (infrastructure problem) This will mark the job as unstable as long as the score is regressing to a negative score. The effect is no reduction to components in that cases. Then no attempt to update other components. Change-Id: I34ff5fb0615bdc0769d19e0c0353084715ded178
Diffstat (limited to 'tcwg_bmk-build.sh')
-rwxr-xr-xtcwg_bmk-build.sh6
1 files changed, 0 insertions, 6 deletions
diff --git a/tcwg_bmk-build.sh b/tcwg_bmk-build.sh
index d3a782a1..88ef5cf9 100755
--- a/tcwg_bmk-build.sh
+++ b/tcwg_bmk-build.sh
@@ -357,12 +357,6 @@ no_regression_p ()
# At this stage, there's no score-based regression.
# We are now checking metric-based regression.
- local score
- score=$(grep -v -E "^#|^$" $run_step_top_artifacts/results | tail -n1)
- # if score is negative, then benchmarking failed and results aren't valid.
- if [ $score -lt 0 ]; then
- return 0
- fi
assert_with_msg "Benchmarking succeeded, but bmk-data is missing" \
[ -e $run_step_top_artifacts/annex/bmk-data ]