[dpdk-ci] CI reliability

[Lincoln Lavoie]

Hi Thomas,

The unit tests that fail are nearly always the same specific unit test.
Aaron addressed some of these in a patch that has yet to be applied to DPDK
(cycles_autotest and test_alarm).  The other one that we still consistently
fail is func_reentrancy_autotest.  It seems like that unit test case can
pass in one run and fail in the next.  We have not been able to determine a
root cause for it yet.  Maybe that is something the devs could help look
into.

Other failures have been caused by DTS.  As part of the plan, we've been
trying to upgrade the DTS deployments on the system, so as the other
changes are made, we can easily pull those in.  However, pulling in the new
DTS version has also pulled in bugs that exist in that version.  For
example, on the stats test suite, it was changed to not skip
the test_xstats_check_vf when no VMs are configured on the system, so when
the overall test suite was being run, it failed on the bare metal where
there are VMs configured right now.  Every time the lab has to upgrade DTS,
we run the risk of introducing these types of failures, which then take
time to debug and fix.

Cheers,
Lincoln

On Wed, Jun 2, 2021 at 3:27 AM Thomas Monjalon <thomas at monjalon.net> wrote:

> I see a lot of failures in the CI, especially unit tests run in UNH IOL.
> It seems to fail for several weeks but did not investigate more.
> What is the cause and what is the plan?
> Should we rely on CI results?
>
>
>

-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie at iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/ci/attachments/20210602/592efc9d/attachment.htm>