On Mon, Jan 11, 2021 at 7:28 PM Lincoln Lavoie wrote: > Hi All, > > How do you want us to handle this in the lab? Can we pull / disable this > unit test from the arm system, ignore it from now (if it's going to be > fixed), disable the unit tests on arm for now (while it's being fixed)? > Maybe it is better to have a "known issue" based skip mechanism to address this in CI. > > Cheers, > LIncoln > > On Mon, Jan 11, 2021 at 8:54 AM Jerin Jacob wrote: > >> On Mon, Jan 11, 2021 at 6:38 PM David Marchand >> wrote: >> > >> > Hey guys, >> > >> > On Mon, Jan 11, 2021 at 9:14 AM David Marchand >> > wrote: >> > > UNH CI is raising failures on a ARM server for the distributor test: >> > > https://lab.dpdk.org/results/dashboard/patchsets/15077/ >> > > >> > > Worker 59 handled 0 packets >> > > Worker 60 handled 0 packets >> > > Worker 61 handled 0 packets >> > > Worker 62 handled 0 packets >> > > Sanity test with non-zero hashes done >> > > === testing big burst (burst) === >> > > line 258: Missing packets, expected 783 >> > > Test Failed >> > > RTE>> >> > > --- stderr --- >> > >> > Looking at the dashboard, I did not see a passing instance of this >> > unit test for ARM. >> > Did it ever work? >> >> No. There are a lot of sync barriers are missing in the distributor >> library. >> Since evendev is kind of replacing this library, we made the fix as >> low priority. >> >> >> >> > >> > >> > >> > -- >> > David Marchand >> > >> > > > -- > *Lincoln Lavoie* > Senior Engineer, Broadband Technologies > 21 Madbury Rd., Ste. 100, Durham, NH 03824 > lylavoie@iol.unh.edu > https://www.iol.unh.edu > +1-603-674-2755 (m) > >