[dpdk-dev] [PATCH] ci: increase unit test timeout

[Michael Santana]

I have been out of the loop for a while, so I do not know how many false 
positives there are. Looking at 
https://travis-ci.com/ovsrobot/dpdk/builds up to two weeks back it seems 
that hash_readwrite_lf_autotest is the only culprit. It looks like it 
lives in the neighborhood of 20-30s seconds so increasing the time out 
for this test seems appropriate as sometimes it halts at exactly 30s 
because of the time out.

Acked-by: Michael Santana <maicolgabriel at hotmail.com>

On 1/28/2020 11:28 AM, Ferruh Yigit wrote:
> Timeout multiplier was 3, which gives 30 seconds for unit test but still
> some unit test was timing out time to time and travis reporting false
> positive failures.
>
> Increasing the multiplier to 10, which makes timeout duration
> 100seconds.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit at intel.com>
> ---
>   .ci/linux-build.sh | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
> index ccc3a7ccd..be3dc4940 100755
> --- a/.ci/linux-build.sh
> +++ b/.ci/linux-build.sh
> @@ -37,5 +37,5 @@ if [ "$AARCH64" != "1" ]; then
>   fi
>   
>   if [ "$RUN_TESTS" = "1" ]; then
> -    sudo meson test -C build --suite fast-tests -t 3
> +    sudo meson test -C build --suite fast-tests -t 10
>   fi