On Thu, Jan 30, 2020 at 12:03 PM Thomas Monjalon wrote:
>
> 28/01/2020 21:53, Aaron Conole:
> > Ferruh Yigit writes:
> >
> > > 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 failur
> > Subject: Re: [dpdk-dev] [PATCH] ci: increase unit test timeout
> >
> > 28/01/2020 21:53, Aaron Conole:
> > > Ferruh Yigit writes:
> > >
> > > > Timeout multiplier was 3, which gives 30 seconds for unit test but
> > > >
; Honnappa
> Nagarahalli
> Subject: Re: [dpdk-dev] [PATCH] ci: increase unit test timeout
>
> 28/01/2020 21:53, Aaron Conole:
> > Ferruh Yigit writes:
> >
> > > Timeout multiplier was 3, which gives 30 seconds for unit test but
> > > still some unit test was
28/01/2020 21:53, Aaron Conole:
> Ferruh Yigit writes:
>
> > 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 durat
Ferruh Yigit writes:
> 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 Yi
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
6 matches
Mail list logo
