DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting Minute - February 17, 2022
Date: Thu, 17 Feb 2022 11:49:20 -0500
Message-ID: <CAOE1vsMK+Ur4Lpru6ZdcOuxS2pbxoZzO1w8jFSaYEGqsZEse-w@mail.gmail.com> (raw)

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

February 17, 2022

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

1. Lincoln Lavoie
2. Aaron Conole
3. Brandon Lo
4. david.marchand@redhat.com
5. msantana@redhat.com
6. lijuan.tu@intel.com
7. alialnu@nvidia.com

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

1. General Announcements
2. CI Status
3. Test Development
4. Any other business

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

=====================================================================
General Announcements

* None

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

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

* Arm is working to send some additional systems into the lab
* AMD has joined DPDK and is working to secure systems to send into the lab
* Subset of RTE flow testing ready to be deployed
   * Limited RTE flow support in testpmd forced a reduction in the test
cases run.  Discussing approaches to extend / add more support / coverage
in testpmd, so we can re-enable the cases.
   * Tests that are compatible with testpmd have seem to have many failures
      * Not suitable for general CI at this time since it would generate
too many false negatives.  Setting up the system to report failures to the
RTE maintainers.
   * There will be bare-metal downtime on Monday, Feb 28, to enable the RTE
testing, which depends on an upgrade to the latest DTS.
* Virtio is being tested internally
   * Seems to require a physical loopback (using a cable) on a single system
   * This is not compatible with many of the community lab systems, and the
test suites may need to be rewritten to accommodate a two system
configuration.
   * Virtio will be deployed on the two compatible systems alongside the
RTE flow deployment
   * The “rewrite” of DTS to support the more general configuration will be
taken as part of the DTS improvements work.
* FIPS test still waiting for review of the patches to DPDK main and DPDK ci
   * Responded to questions from reviewers last week, but no further
response
   * Sent out a follow up email this morning
* Coverity upgraded to 2021.12
   * Created 77 new issues and closed 50 issues reported by the older tool.
* Sonar Cloud scanning has also been turned on, follows similar frequency
to Coverity
   * Reports are being sent to the dev mailing list.
   * If you’d like to be added to the DPDK organization on the web
interface, please let us know, and we can add your account.
* Working to finalize the 2022 SOW objectives this week, followed by final
review by the tech board & governing board.

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

* Focused on the RC1 validation for 2022.03.  Running into issues with the
icc builds, being discussed in techboard currently.
* Run into issues with 2019.11 compile, there is a module libtmp-net-ice,
the fix can’t be back ported to the older LTS branch. Those tests are now
disabled on that module.
* RC1 reports have been sent up to the release meetings.

---------------------------------------------------------------------
Github / OBS

* No updates, the team hasn’t had time to come back to finish up the OBS
scripts.
* Container based build in Github actions based distro based building can
be “flaky” based on container image pulls (if the pull fails, it looks like
the build fails). OBS is likely the better approach for distro based
building.

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

* DTS improvement WG is continuing to meet:
https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit#
* Next meeting is February 23, 2022, 2pm UTC
https://armltd.zoom.us/j/97503259680?pwd=VVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=addon

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

* Next Meeting: March 3, 2022
* Note, March 17, Lincoln will be on vacation, need someone to chair the
meeting.


-- 
*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: 5711 bytes --]

                 reply	other threads:[~2022-02-17 16:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAOE1vsMK+Ur4Lpru6ZdcOuxS2pbxoZzO1w8jFSaYEGqsZEse-w@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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git