> -----Original Message----- > From: David Marchand <[email protected]> > Sent: Friday, November 12, 2021 2:16 PM > To: Lincoln Lavoie <[email protected]> > Cc: Dumitrescu, Cristian <[email protected]>; dev > <[email protected]>; Aaron Conole <[email protected]>; Thomas Monjalon > <[email protected]>; Yigit, Ferruh <[email protected]>; > [email protected] > Subject: Re: [dpdk-dev] [Bug 826] red_autotest random failures > > On Fri, Nov 12, 2021 at 3:11 PM Lincoln Lavoie <[email protected]> wrote: > >> This failure keeps on popping in the CI. > >> The bug report is one month old, with no reply. > >> > >> > >> I sent a proposal of removing red_autotest from the list executed by the > CI. > >> https://patchwork.dpdk.org/project/dpdk/patch/20211027140458.2502- > [email protected]/ > >> > >> It might be the best solution waiting for an analysis. > >> > >> > >> -- > >> David Marchand > >> > > > > Hi David, > > > > My understanding is, removing the test would require removing it from the > DPDK unit tests, we are just running the fast-tests suite for the unit tests. > DPDK's unit test structure / framework does not allow removing or > customizing the suite of tests beyond the suites. > > https://patchwork.dpdk.org/project/dpdk/patch/20211027140458.2502-2- > [email protected]/ > > > > > > In the lab, Brandon has been looking into and trying different > configurations for running the tests within the containers along the lines of > the CPU pinning requirements that might be assumed by the unit tests. So > far, everything he has tried has still had the similar failures / issues. We > are > still looking into it, so the bug is not sitting without action, just no final > resolution. > > The mail I sent was not a comment for the investigation on UNH side. > The ask is for Cristian to have a look too. > > > -- > David Marchand
Wojciech, Megha, Are you able to take a look at why is the RED autotest failing, please? Thanks, Cristian
