test suite reviews and discussions
 help / color / mirror / Atom feed
From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org, dev <dev@dpdk.org>
Subject: DTS Improvement Working Group Minutes (March 2)
Date: Wed, 9 Mar 2022 09:04:02 -0500	[thread overview]
Message-ID: <CAHx6DYB9CvQt1n8HC_dUx7iGNn7QbAcpPDskdu_OC9qOq4wikA@mail.gmail.com> (raw)

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

Attendees

   -

   Owen Hilyard
   -

   Honnappa Nagarahalli
   -

   Lijuan Tu
   -

   Lincoln Lavoie

Agenda

   -

   Additions to the agenda
   -

   Review/Carry forward pending action items
   -

   Review DTS DPDK Modifications excel sheet
   -

   Merging DTS into DPDK
   -

   Review additional work items

MinutesReview/Carry forward pending action items

   -

   Honnappa - Patches to DPDK to address changing the constants and printfs
   under progress.
   -

      Still in progress
      -

   Honnappa - The changes to DPDK need to be backported to LTS releases.
   Discuss with Lijuan and the community.
   -

      Patches will be backported
      -

   Owen - Owen to review Juraj’s feedback.
   -

      Done
      -

   Honnappa - Follow up with DPDK governing board to get the approval/legal
   opinion on including the GPL licensed files from DTS in the DPDK tree.
   -

      Governing board has not met
      -

   Owen - Look at making DTS build using the common DPDK repo in addition
   to the existing tarball option.
   -

      Looks to be possible, blocked by decisions on the placement of DTS
      inside of DPDK
      -

   Lijuan - The makefile removal patch is ready to get merged (
   http://patchwork.dpdk.org/project/dts/list/?series=20610). Merge it in
   the 22.03 DTS release.
   -

      Additional issues discovered
      -

         Meson configuration changed improperly
         -

      Makefiles will be removed as the meson issues are fixed
      -

   Juraj - Postponed: Convert the makefile build for documentation to use
   meson build after merging the repositories or the directory structure is
   known.
   -

      Not present
      -

   Honnappa - Discuss merge permissions for Owen for the DTS tree with the
   Tech Board
   -

      Merge permissions have been granted
      -

   Lijuan/Owen - Check if dep/scapy_modules/Dot1BR.py file is required to
   be in DTS. If it is required, understand options for replacement/removing
   this file.
   -

      Look into rewriting the file so it’s not GPL
      -

   Lijuan/Owen - Check if dep/QMP/qmp.py can be installed on DUT as part
   of  the qemu-guest-agent package.
   -

      In progress
      -

   Honnappa/Owen - Discuss Python bindings for DPDK in March 9th Techboard
   call.
   -

      Meeting has not happened yet

Merging DTS into DPDK

   -

   Are we going to integrate DTS with the DPDK build system? No resolution
   yet.
   -

   Try for 22.07
   -

   Focus on framework and test cases used in CI
   -

   Do a deep dive on Feb 9th - identify what needs to be done and estimate
   the work.


DPDK Modifications Review

   -

   Some issues are fixed
   -

   Many changes are still present.

Action Items

   -

   Honnappa - Patches to DPDK to address changing the constants and printfs
   under progress.
   -

   Owen - Write a script to run formatters (Black + Isort). Pin versions in
   dts requirements file. As part of the patch series, format DTS again.
   -

   Jurai - Rewrite dep/scapy_modules/Dot1BR.py from scratch so we can
   change the license.
   -

   Lijuan/Owen - Check if dep/QMP/qmp.py can be installed on DUT as part
   of  the qemu-guest-agent package.
   -

   Lijuan/Owen - Remove ABI_stable test suite
   -

   Lijuan/Owen - Investigate DTS test suites to check for redundant tests
   -

      Unit testing (handled by meson now)
      -

      “Does it compile?” tests
      -

      etc

Any other business

   -

   Next Meeting: March 9, 2022

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

                 reply	other threads:[~2022-03-09 14:04 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=CAHx6DYB9CvQt1n8HC_dUx7iGNn7QbAcpPDskdu_OC9qOq4wikA@mail.gmail.com \
    --to=ohilyard@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=dts@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).