From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: "ci@dpdk.org" <ci@dpdk.org>, "dts@dpdk.org" <dts@dpdk.org>
Subject: DTS WG Minutes 3/23/22
Date: Wed, 23 Mar 2022 14:24:23 +0000 [thread overview]
Message-ID: <c7543eae638c4d1fbe571f9a77c6bc60@pantheon.tech> (raw)
[-- Attachment #1: Type: text/plain, Size: 3677 bytes --]
Hello folks,
Please find the WG meeting minutes below:
Attendees
* Honnappa Nagarahalli
* Lijuan Tu
* Juraj Linkes
* Owen Hilyard
Agenda
* Additions to the agenda
* Review/Carry forward pending action items
* Merging DTS into DPDK
* Review DTS DPDK Modifications excel sheet
* Review additional work items
Minutes
Review/Carry forward pending action items
* Honnappa - Patches to DPDK to address changing the constants and printfs under progress.
* Still in progress
* Are the GPL files part of the framework or test cases?
§ Qemu-ga-client, qmp.py - are part of the framework used with VM based test cases. DTS uses these to communicate with VMs.
§ These files will be moved out of DTS into a separate repo. Honnappa to discuss with the Techboard on where to host the repo.
§ Owen - looking to see how to get Qemu-ga-client, qmp.py into DTS
§ Lijuan - texttable.py - found a library and is working on integrating it.
* 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.
* Still in progress (work left on < 5 test suites, target to get this done in 2 weeks)
* Owen - Write a script to check if the formatters are throwing any errors.
* The responsibility of submitting the well formatted code is with the patch submitter
* The script should inform the developer what are the errors and suggest running the formatter script
* Lijuan will enable this script in CI
* Owen - Investigate DTS test suites to check for redundant tests
* Unit testing (handled by meson now) - Can be removed, but we will add a deprecation notice for the next release, and will be removed in the release after that.
* "Does it compile?" tests - These are removed already
Merging DTS into DPDK
* Try for 22.07 RC1
* Focus on framework and test cases used in CI
* Juraj has created a RFC patch to move the DTS framework to DPDK repo. Juraj to share this with DTS WG directly for further discussion.
* AI Juraj - Try to split the RFC patch into logical parts.
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.
* Lijuan - Check to see if texttable.py can be replaced with Python libraries.
* Owen - Add a deprecation notice to release notes and a warning in DTS to remove the unit testing from DTS.
* Honnappa - Review the must have list from https://docs.google.com/spreadsheets/d/1s_Y3Ph1sVptYs6YjOxkUI8rVzrPFGpTZzd75gkpgIXY/edit#gid=1128536548 to ensure correct priority
* Lijuan - To create the DTS test suite developer document.
* Juraj - Review the DTS user guide to ensure the identified items in must have are incorporated.
* Lijuan - Submit a patch for TestSuite_efd.test_perf_efd_valuesize to use the -c_args option in meson configure command
* Honnappa - Discuss the possibility of the GPL file repo hosted under dpdk.org with the techboard. An alternate approach is to use git submodules, not sure if this solves the GPL issue.
* Owen - Add a script/makefile/meson get Qemu-ga-client, qmp.py into DTS at run time.
* Owen - Write a script to check if the formatters are throwing any errors.
* Lijuan - Review and merge the pylama config patch.
* Lijuan - Unpack tcl tools (needed for IXIA), store in dep/<directory>, test and submit a patch.
Any other business
* Next Meeting: March 30, 2022
[-- Attachment #2: Type: text/html, Size: 35842 bytes --]
reply other threads:[~2022-03-23 14:24 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=c7543eae638c4d1fbe571f9a77c6bc60@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=ci@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).