From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] Community CI Meeting Minutes - September 23, 2021
Date: Thu, 23 Sep 2021 12:03:50 -0400 [thread overview]
Message-ID: <CAOE1vsPqsSGxZ4JJersJ_846qP8H67zyAQMOiVz5eGtPEGdswA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3695 bytes --]
DPDK Community CI Meeting Minutes
September 23, 2021
##########################################################################
Attendees
1. Lincoln Lavoie
2. Ashley Weltz
3. David Marchand
4. Ali Alnubani
5. Michael Santana
##########################################################################
Agenda
1. CI Status
2. Test Development
3. Any other business
##########################################################################
Minutes
==========================================================================
General
* Setting up DPDK Slack Workspace, use the following link to join:
https://join.slack.com/t/dpdkproject/shared_invite/zt-v6c9ef5z-FqgOAS7BDAYqev_a~pbXdw
CI Status
--------------------------------------------------------------------------
UNH-IOL Community Lab
* Ready to deploy an internal system to periodically refresh Docker images
* This will also update the ABI references to prevent false failures
* Refactoring Jenkins pipelines to increase efficiency of testing
* We are actively working on reducing the backlog by optimizing
allocation of resources within Jenkins
* Bare-metal downtime last week due to:
* TRex ignoring return values indicating an error
* This causes segfaults on any card with an xstats count > 0
* It took a substantial amount of time to track this down
* Upstream patch generated to TRex:
https://github.com/cisco-system-traffic-generator/trex-core/pull/761
* Changes to DTS since the last update requiring re-testing
* Bare-metal status
* Mellanox and Broadcom on ARM are non-functional. All other NICs should
be reporting up.
* Mellanox systems updated to the latest versions of TRex (bug above
didn’t impact that system), other systems were rolled back to known working
versions.
* Mellanox pass/fail criteria updated to 1.5%, per their request.
* TRex and a couple of DTS bugs (divide by zero was reintroduced) will
need to be patched, before upgrades can proceed.
* FreeBSD 13.0
* Fix for 1 of the two unit test issues has been submitted:
http://patches.dpdk.org/project/dpdk/patch/20210917150917.90892-1-bruce.richardson@intel.com/
* ABI failure 20.11
* Need to investigate / confirm ABI failure for
https://lab.dpdk.org/results/dashboard/tarballs/16879/
--------------------------------------------------------------------------
Intel Lab
* pf_smoke / test_pf_rss test case has been disabled, while waiting for a
fix to be merged into the mainline. Fixed has been merged into next-net,
and should be in mainline by the end of the week. Need to make sure we
notify the Intel lab team to re-enable the test.
--------------------------------------------------------------------------
Github Actions & OBS
* OBS working on the final revisions for the patch.
* Github Actions and zero-day bot is currently down. Server hosting the
service had a hardware failure (occurred Monday). Should be restored by
next week. The team has backups of the VM running the jobs.
==========================================================================
Test Development
* Finished categorizing the feedback DTS. Creating an Excel (Google Sheet)
issue tracker, so developers can be assigned, this may then be ported into
Bugzilla
* Next DTS Meeting: TBD
==========================================================================
Any other business
* Next Meeting: October 7, 2021
--
*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: 5000 bytes --]
next reply other threads:[~2021-09-23 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 16:03 Lincoln Lavoie [this message]
2021-09-24 17:31 ` Brandon Lo
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=CAOE1vsPqsSGxZ4JJersJ_846qP8H67zyAQMOiVz5eGtPEGdswA@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).