From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: Community CI Meeting - March 3, 2022
Date: Thu, 3 Mar 2022 10:33:53 -0500 [thread overview]
Message-ID: <CAOE1vsN30OFipLYDXsvyy+HMM5u5uAHhfiiL22v4+En-MRftVg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3842 bytes --]
March 2, 2022
#####################################################################
Attendees
1. Lincoln Lavoie
2. Brandon Lo
3. Aaron Conole
4. Liang-min "Larry" Wang
5. Michael Santana
6. Lijaun Tu
#####################################################################
Agenda
1. General Announcements
2. CI Status
3. Test Development
4. Any other business
#####################################################################
Minutes
=====================================================================
General Announcements
* Nothing specific for this meeting
=====================================================================
CI Status
---------------------------------------------------------------------
UNH-IOL Community Lab
* Working on deploying test coverage measurements (lcov / gcov) for the
unit testing. First need to get this running stable within the test, then
work on a solution to parse / store metrics to track over time.
* FIPS work is continuing, working with members from Intel to get all other
algorithms working with the ACVP API.
* RTE Flow & VirtIO should be deployed.
* VirtIO can only be run on the Intel NIC x86_64 systems until DTS
upgrades generalize the required test topology.
* RTE Flow is running periodically, until some failures can be
addressed. Emails are being sent to RTE flow maintainers.
* SOW for 2022 is going to the governing board for final review on March 8.
---------------------------------------------------------------------
Intel Lab
* Removed the icc_build for cntx modules in the CI.
* Found some issues with patches that were missing the Series ID.
* Seems like there might be a bug in patchworks.
* An Example:
http://patches.dpdk.org/project/dpdk/patch/20220217150239.69876-1-bruce.richardson@intel.com/
* It seems like, without the Series ID, all testing and checks are
missing the patch, including the check patch scripts.
* Lincoln to reach out to Ali Alnubani about the issue, will copy Lijuan
and Aaron.
* Around the RC1, there will be a lot of patches to be tested / queued.
Intel is receiving a 502 error from the server sometimes (fairly
frequently).
* May be caused by polling vs event subscription. Can try to lower the
frequency or change the back off time.
* Aaron confirmed the github action scripts see that occur sometimes and
have a recovery built into wait and then try again.
---------------------------------------------------------------------
Github Actions & OBS
* No updates, maintainers tied up in other products for the time-being.
=====================================================================
Test Development
* DTS improvements work is still ongoing, aiming to migrate DTS test suite
into the DPDK repo for the 22.07 release
* Work is in progress to fix test suites that directly modify DPDK source
code before compile / test run.
* Working on tool chains for developers, including lint and static analysis
for python (DTS’ language).
* Dropping / removing redundant test suites (there was an ABI test and some
calls to unit testing).
* Next Meeting: March 9, 2022
*
https://armltd.zoom.us/j/97503259680?pwd=VVlmWnlnTXJkVGkwR2JOU3R3b3Vndz09&from=addon
* Notes:
*
https://docs.google.com/document/d/1E2mkTHNQ5vyln1JvnJTil15cjacUTXP7LXb9K960Vxs/edit#heading=h.12ft7412ly1n
=====================================================================
Any other business
* Next Meeting: March 17, 2022
* Note, Lincoln will be on vacation during this week
* Aaron will be chairing 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: 5145 bytes --]
reply other threads:[~2022-03-03 15:34 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=CAOE1vsN30OFipLYDXsvyy+HMM5u5uAHhfiiL22v4+En-MRftVg@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).