The unit test time out setting was the same for jobs on different
platforms. Due to difference of running environments, platforms
could have different time out expecations.
Provide TIMEOUT_FACTOR as a knob to change the time out setting.
Signed-off-by: Ruifeng Wang <ruifeng.w...@arm.com>
Reviewed-by: Gavin Hu <gavin...@arm.com>
---
.ci/linux-build.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
index d079801d7..b653de97c 100755
--- a/.ci/linux-build.sh
+++ b/.ci/linux-build.sh
@@ -96,5 +96,6 @@ if [ "$ABI_CHECKS" = "1" ]; then
fi
if [ "$RUN_TESTS" = "1" ]; then
- sudo meson test -C build --suite fast-tests -t 3
+ TIMEOUT_FACTOR=${TIMEOUT_FACTOR:-3}
+ sudo meson test -C build --suite fast-tests -t $TIMEOUT_FACTOR
fi
--
2.17.1
