DPDK CI discussions
 help / color / mirror / Atom feed
* [dpdk-ci] Community CI Meeting Minutes October 21, 2021
@ 2021-10-21 20:06 Lincoln Lavoie
  0 siblings, 0 replies; only message in thread
From: Lincoln Lavoie @ 2021-10-21 20:06 UTC (permalink / raw)
  To: ci

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

October 20, 2021

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

1. Lincoln Lavoie
2. Ali Alnubani
3. Aaron Conole
4. Ashley Weltz
5. Juraj Linkeš
6. Michael Santana

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

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

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

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

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

* Spell check dictionary / exceptions location, CI repo or within dpdk main
repo?
   * Look into moving the scripting to run the spell checker into the main
repo, as part of devtools, then allow the dictionary / exceptions
definition to live alongside those tools.
* Periodic dashboard update still to roll out, currently in final Internal
reviews, aiming for Monday, October 25.
   * Plan to use this as a test of the monitoring services for the lab,
i.e. the dashboard going off-line will trip the email notifications.
* Container images are now set up to automatically refresh (i.e. “OS”
patches) every first Monday of the month.  First automated run will be
November 1, around 9am Eastern USA time.
* Fix proposed to limit the number of cores used for unit testing, which
may be the reason the arm based hosts appeared to have more intermittent
failures (i.e. high core count).
https://patchwork.dpdk.org/project/dpdk/patch/20211019112602.17782-1-david.marchand@redhat.com/
* Brandon is still working through the FIPS test harness to automate the
collection of vectors from NIST systems.
* Is the arm SVE job in an emulated environment still disabled? What can we
do to speed it up?
   * This is still disabled, based on run time.
   * Could this be setup to build the binaries as a cross-compile, then run
on the required tests within this emulated environment on those binaries.
* i40e scatter test has been intermittently failing in the DTS testing.
Aaron Conole is planning to reach out to the maintainter to check if this
has been noticed / looked at, etc.

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

* No updates were available.

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

* Merged the OBS support, next steps are to setup the repo (in OBS, not a
git repo proper). Aiming to get this finished up before the end of the year
(not sure of the amount of work needed to clean up the scripts running in
the OBS build processes).
* Still waiting on the arm-application that will provide access to the arm
systems, Aaron and team can’t final review the proposed changes to the yaml
without that information.

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

---------------------------------------------------------------------
DTS Improvements

* Techboard discussed the proposal.  Honnappa should be following up with a
meeting of the improvements team.

---------------------------------------------------------------------
DPDK Symbol Bot

* Proposed on the mailing list:
https://mails.dpdk.org/archives/ci/2021-September/001368.html
* Questions raised:
   * 1. Does moving it to CI make sense to folks?
   * 2. In CI, how do I pick up and use the get-maintainer.sh script from
DPDK.
   * 3. In CI, where do I find the DPDK repo?
* Need to review / look at the scripts to see what assumptions have been
made, such as, cwd is the top of the dpdk git repo, or similar?  What tools
are needed, etc.
* Need to identify what the proposed “results” are, i.e. any expired
experimental symbols cause a failure, etc.
* Scripts in CI should probably not send emails directly, rather rely on
the CI to do that notification.
* Larger question / idea is a way to allow triggering additional checks
(like this test) on specific repos / branches, as a “milestone” type case.

---------------------------------------------------------------------
SPDX checking

* Request to run the devtools/check-spdx-tag.sh as part of the CI process.
* Any objections to adding this to jobs currently running as the
“checkpatch” or do we want to create a stand alone context for the reports?
* Ali Alnubani currently oversees the running / reporting of checkpatch,
script is in the dpdk-ci repo /tests/checkpatch.sh.  Lincoln Lavoie will
look at proposing a patch to add the check to the test.

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

* Next Meeting: November 4, 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: 6054 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-10-21 20:07 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-10-21 20:06 [dpdk-ci] Community CI Meeting Minutes October 21, 2021 Lincoln Lavoie

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).