Re: [dpdk-ci] Community CI Meeting Minutes - January 14, 2021

[David Marchand <david.marchand@redhat.com>]

Sorry I did not attend.

On Thu, Jan 14, 2021 at 5:14 PM Lincoln Lavoie <lylavoie@iol.unh.edu> wrote:
> #################################################
> Minutes
>
> =================================================
> CI Status
>
> -------------------------------------------------
> Intel Lab
>
> * Smoke tests are now enabled and results are being included in the reports to patch works.  Running about 6 test cases right now.  Check the patchworks reports for the specific details (showing up as intel-test in pathworks as the label).  Recommend to add a link to the DTS test plan into the reports for each of the test cases that are being run.
> * Merge coming for pmdinfogen, which will add some additional python dependencies.  Labs (UNH and Intel) will need to add these into the test systems / DUTs where necessary: https://patches.dpdk.org/cover/81614/

Since it blocks those changes from being merged in the main repo, can
we (Thomas or I) get a heads up when all systems are ready?


>
> -------------------------------------------------
> Github Actions / Travis CI / OBS
>
> * Github Actions have been running for about 1 month.  Working on automating the process of checking the output and posting the results to patchworks.  ETA is probably about 1 to 2 weeks away.
> * Planning to keep Travis CI around for now, specifically for the ARM builds.  Hopefully, the amount of “free execution time” will be enough to cover the ARM builds.

I am not sure we will have enough credits, but ok, why not.


> * OBS, still need a mechanism for timing out branches.  This will get worked on once the Github Action work is completed.  Will take 2 to 4 weeks, once started.
>
> -------------------------------------------------
> UNH-IOL Community Lab
>
> * We are aware of pending patchsets on the dashboard and will be investigating those today.
> * Arm machines are now running compile and unit testing.
> ** Now focusing on implementing functional and performance testing using the NICs installed in the machine.
> ** Broken unit test case: https://bugs.dpdk.org/show_bug.cgi?id=612
> * Mellanox systems are now running functional testing; we are currently monitoring these results for false negatives.  We need to double check it sent an updated report to patchworks.
> * Feature request: how could maintainer request rerun of jobs, possibly through the dashboard.
> * Implemented a failure alert system to detect false failures quicker.
> * Testing failures will now report the last 20 lines of log output, example is here: http://mails.dpdk.org/archives/test-report/2021-January/174069.html

Thanks!
I noticed today, it is a small improvement, but it will save us some
time when looking at the reports.

Just a comment on this example, we can only see the Ubuntu SPDK
failure and not the other failures, is this expected?


-- 
David Marchand