DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] Community CI Meeting Minutes - July 29, 2021
Date: Thu, 29 Jul 2021 10:45:47 -0400	[thread overview]
Message-ID: <CAOE1vsNG4_nWE-gDC_vShqmNnr-6kO-4Mt4Ktf=5MsODU_AjCg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 5377 bytes --]

DPDK Community CI Meeting Minutes

July 29, 2021

#####################################################################
Attendees

1. Lincoln Lavoie
2. Henry Nadeau
3. Owen Hilyard
4. Brandon Lo
5. Ali Alnubani
6. Aaron Conole
7. Juraj Linkeš
8. Lijuan Tu
9. Ashley Weltz
10. Michael Sanata

#####################################################################
Agenda

1. CI Status
2. Test Development
3. Any other business

#####################################################################
Minutes

=====================================================================
CI Status

---------------------------------------------------------------------
UNH-IOL Community Lab

* Mellanox performance testing testing is back online
* Currently working on expanding functional testing back to previous
working coverage on the bare-metal systems.
   * Some tests will require patch submissions to DTS (in process)
   * Currently working on MTU update
* Performance test reporting stabilized after 1C/2T migration and migration
to percentage changes.
* Alpine linux fails to build performance-thread example
   * Bugzilla https://bugs.dpdk.org/show_bug.cgi?id=756
* FreeBSD 13 unit test failures
   * Bugzilla https://bugs.dpdk.org/show_bug.cgi?id=761
* Looking to split up test reports for faster and more digestible
patchworks results
   * Will aim to split up along two dimensions of compile / unit and
architecture (aarch64 and x86_64).  Note, cross-compile lives with the
target architecture.
* FreeBSD 13 ABI tests back in production
* Arm unit testing back in production
   * Cppc_cpufreq kernel module was causing failures
* Documentation spell check has been deployed into the lab, runs
automatically if changes in the documentation directories are made
   * Patch to fix initial errors is submitted:
https://patchwork.dpdk.org/project/dpdk/patch/20210726164919.39986-1-hnadeau@iol.unh.edu/
   * Just need to finalize reporting up to patchworks.
* Requests to add two more jobs, aarch32 cross-compile target from x86_64,
run unit / compile testing using clang on native aarch64.  Lab will get
these into the queue and will aim for the end of the summer (best initial
estimate).

---------------------------------------------------------------------
Intel Lab

* Patchwork Series https://bugs.dpdk.org/show_bug.cgi?id=718
   * Changed Intel CI not to create patch series out of patchwork.
   * Intel CI just follows patchwork.
   * This is a user issue, users should send patches with in-reply-to the
right message-id.
* DTS-CI has been set up
   * Document building will based on test_plans and doc/dts_gsg
   * Suite and Framework will be tested on Intel 710 series and E810 series
cards.
      * Framework changes are checked with a couple of smoke test suites.
      * Suite changes run the specific suite, but not other changes.
      * Lijuan will start a discussion on the DTS mailing list for what
test suites are used for testing the framework.
   * Patchwork needs to be set up to monitor this dts-test-report@dpdk.org.
   * Ali is busy with other activities, so will use test-report@dpdk.org as
a workaround.
   * http://mails.dpdk.org/archives/dts-test-report/2021-July/000020.html
   * http://mails.dpdk.org/archives/dts-test-report/2021-July/subject.html
   * aweltz@linuxfoundation.org might help to add the email list onto the
webpage https://www.dpdk.org/contribute/#mailing-lists

---------------------------------------------------------------------
Github Actions & OBS

* OBS scripts need a little bit of a redesign, but are close, should be
completed by next week.
* Github Action, no news is good news.
* There are a couple issues with the workflows used by Github Actions,
these don’t currently impact DPDK.  These are being fixed, so multi
workflows will get reported.  There is also an issue, where the email logs
are only included for the first failure, they can get the full logs via the
links.  Aaron and team are working on fixing both of these.
* Scripts for patchworks have been moved to under the OVS robot account.

=====================================================================
Test Development

* func_reentrancy_autotest is still failing randomly, without a pattern on
architecture (x86_64, aarch64), operating system, or compiler (gcc,
clang).  Aaron has a patch to improve the debugging / reporting on the
test.  This should be posted next week and should help with debugging.
* DTS Improvements
   * Discussions are progressing. Work is being tracked here:
https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit
   * Next Meeting: August 4, 2021
   * UNH-IOL is working on a series of patches to DTS to fix issues
introduced into the MTU test suite and the stats test suite.

=====================================================================
Any other business

* Next Meeting: August 12, 2021
* There were some changes to the Mellanox performance testing
configuration, Ali / Owen have a thread to confirm the DTS configurations
are as Mellanox expects.

-- 
*Lincoln Lavoie*
Principal 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)
<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 7111 bytes --]

             reply	other threads:[~2021-07-29 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 14:45 Lincoln Lavoie [this message]
2021-07-29 15:17 ` Thomas Monjalon
2021-07-29 18:55   ` Brandon Lo
2021-07-30  6:36     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOE1vsNG4_nWE-gDC_vShqmNnr-6kO-4Mt4Ktf=5MsODU_AjCg@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).