On Fri, Nov 12, 2021 at 8:52 AM David Marchand <david.march...@redhat.com> wrote:
> On Fri, Oct 8, 2021 at 9:24 AM <bugzi...@dpdk.org> wrote: > > > > https://bugs.dpdk.org/show_bug.cgi?id=826 > > > > Bug ID: 826 > > Summary: red_autotest random failures > > Product: DPDK > > Version: unspecified > > Hardware: All > > OS: All > > Status: UNCONFIRMED > > Severity: normal > > Priority: Normal > > Component: other > > Assignee: cristian.dumitre...@intel.com > > Reporter: david.march...@redhat.com > > CC: dev@dpdk.org, jasvinder.si...@intel.com > > Target Milestone: --- > > > > A recent failure can be found at: > > https://lab.dpdk.org/results/dashboard/patchsets/19223/ > > > > 50/94 DPDK:fast-tests / red_autotest FAIL > 0.86s > > exit status 1 > > > functional test 6 : use several queues (each with its own run-time data), > use several RED configurations (such that each > configuration is sharte_red by multiple queues), > increase average queue size to target level, > dequeue all packets until queue is empty, > confirm that average queue size is computed correctly > while queue is empty > (this is a larger scale version of functional test 3) > > queue config q avg before q avg after expected > difference % tolerance % result > 0 0 1022.0000 1022.0000 1016.0627 > 0.5843 5.0000 pass > 1 0 1022.0000 1022.0000 1016.0627 > 0.5843 5.0000 pass > 2 1 1022.0000 1022.0000 1010.1483 > 1.1733 5.0000 pass > 3 1 1022.0000 937.1660 1010.1483 > 7.2249 5.0000 fail > > -------------------------------------<fail>------------------------------------- > > > > 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-2-david.march...@redhat.com/ > > 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. 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. Cheers, Lincoln -- *Lincoln Lavoie* Principal Engineer, Broadband Technologies 21 Madbury Rd., Ste. 100, Durham, NH 03824 lylav...@iol.unh.edu https://www.iol.unh.edu +1-603-674-2755 (m) <https://www.iol.unh.edu>
