DPDK CI discussions
 help / color / mirror / Atom feed
* [dpdk-ci] Community CI Minute - August 13, 2020
@ 2020-08-18 15:46 Lincoln Lavoie
  0 siblings, 0 replies; only message in thread
From: Lincoln Lavoie @ 2020-08-18 15:46 UTC (permalink / raw)
  To: ci

August 13, 2020

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

1. Lincoln Lavoie
2. Trishan de Lanerolle
3. Brandon Lo
4. Ali Alnubani
5. Daniel Kirichok
6. David Liu
7. James Hendergart
8. Juraj Linkes
9. Lijuan Tu
10. Ruifeng Wang
11. Tomasz Zawadzki
12. Zhaoyan Chen

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

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

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


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

* TravisCI
   * BUG-508 on missing results in TravisCI, no updates from Aaron yet.
   * Update from Aaron (8/18): Need to resync with David - this
happened a couple of times due to the travis API server going down.  I
think it's resolved, but need to double check.

* OBS
   * Integration is still ongoing, Aaron was working on this, so OBS
builds / tests would be started from the same robot driving the
TravisCI processes.
   * Update from Aaron (8/18): Haven’t gotten a chance to work on this
again, due to supporting a customer issue.

* Intel Lab
   * Moved build results to appear with the last patch in a patch set.
   * Still working on the change caused by the branch name change
master -> main.  Zhaoyan will update a bug / ticket for tracking this
if needed.

* UNH-IOL Community Lab
   * Currently working on deploying the functional tests onto the
bare-metal machines.  8 test cases running on Intel 40G, 6 running on
Intel 10G, 5 on Broadcom 25G.
      * Setting up a script that will email functional test results in
a separate email for patchworks to consume.
      * Currently, the results from functional tests are publicly
shown on the lab.dpdk.org dashboard.
      * How should this be separated in patchwork reports (i.e. one
report for functional testing across all bare-metal platforms, or one
report per bare-metal platform like the performance cases)?
         * Group agreed to aim for separate reports for each
bare-metal platform.
   * Also working on Broadcom 100G NIC to get performance and
functional tests running.
   * Tracking an issue with pause settings on the Mellanox systems,
where the settings are being changed. Work around in place to set
these back to the correct values before the test, but need to identify
the root cause.

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

* Completed Features
   * MTU Update
   * Basic stats
   * Speed Capabilities
   * Checksum offload checks
   * Multicast Mac Filtering
   * RSS Key Update
   * L3 and L4 Checksum Offload
   * Multicast mac address filter
   * Linux Kernel Module VFIO Testing (new)
   * Linux Kernel Module UIO Testing (new)
   * FW Version (new, not yet merged)

* Features In Progress
   * Speed Capabilities
      * Pending updates to testpmd (BUG-496), just keeping here to
track status, etc.
   * Rx Interrupt
      * Email out to the community for testpmd features to perform an
interrupt and some clarification on how to handle the interrupt. Along
with some testing ideas to test this feature.
   * QinQ offload
      * Investigating existing DTS Test Suites (there are multiple
QinQ related ones) include this feature in testing to confirm the
extent that NICs support those test implementations.  If necessary,
we’ll create a more generic approach to testing QinQ that best
supports multiple NICs, etc.

* Features Next Up
   * Inner RSS (medium priority feature)
   * Module EEPROM Dump (medium priority feature)
   * Then will likely look to extending tests for the rte_flow mode and APIs.
   * Feature / Development Tracking:
https://docs.google.com/spreadsheets/d/1xeGQZdt6R3FrxMUSfbLRMKObDs7yGEODuXSLw4OjSco/edit#gid=818973396

* Deployment of Functional Test Cases in UNH-IOL
   * Beyond the tests created by UNH-IOL, many of the existing DTS
cases have been verified and will also be deployed (39 total)
   * Tests are currently running on Intel bare-metal (6 tests running
on 10G and 8 tests running on 40G)
   * Internal testing of 5 functional cases on Broadcom 25G, will be
moving to production reporting by the end of this week.

* Board meeting reporting
   * Next meeting is scheduled Monday, August 17, 2020, and James is
giving a status update on the development.
   * Community members are encouraged to provide input on the
development, how they feel it has progressed or ideas about if / how
it should continue.  This is related to the ideas around test
requirements with features submission.

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

* Next Meeting: August 27, 2020 1pm UTC
* Blog on DPDK CI approaches:
https://docs.google.com/document/d/1eV1YCoi28ArNOK8godYbnDzvcSbU5_SUtX4rMqGwCPY/edit
* From James: Test development requirements with new feature
submissions in DPDK proper.
* SPDK release: release completed, need to update the community lab to
pull the latest release for testing DPDK change.


-- 
Lincoln Lavoie
Senior 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)

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

only message in thread, other threads:[~2020-08-18 15:47 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-18 15:46 [dpdk-ci] Community CI Minute - August 13, 2020 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).