Re: [dpdk-dev] [Bug 826] red_autotest random failures

[Brandon Lo <blo@iol.unh.edu>]

On Wed, Mar 9, 2022 at 5:01 AM Danilewicz, MarcinX
<marcinx.danilewicz@intel.com> wrote:
>
> Hi Brandon,
>
> Sorry for late response, but I was busy in mean time. But after your mail well .. I've tried to run test dpdk from docker image. Few instances of images in parallel, enough to get machine fully loaded. But in turn, red_autotest never failed.
>
> Is it possible for you to share some additional details? About hardware used for testing, memory sizes, etc. To get some hint how to get these failures. I've seen other test failing constantly, depending on machine I was running other autotests. Maybe tests before red_autotest are changing hardware to the state where red_autotest is failing. Anyone tried to change autotests execution order?

Hi Marcin,

Unfortunately, I don't have any more details other than the ones we
talked about before. It is possible that the issue is not as common
now that we limited the number of compile jobs that can happen on each
machine at the same time.
We limited the amount of RAM that each job can use again so that the
systems are not getting a high load.

> Also, I've don’t almost all to reproduce error and perhaps it is better to ignore that random error for now. It looks like you are able to successfully pass that test all the time, even when is failing from time to time. Right? If that is the true error, it will come out elsewhere.

Yes, I think it's ok if you think the test is good for now. I haven't
seen it fail in a while, so it might just be due to the load we put on
the systems.
If the issue comes up, I can contact you again.

Thanks,
Brandon



--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu