Brandon Lo
Trishan de Lanerolle
James Hendergart
Juraj Linkes
Reyfone Wang
Tomasz Zawadzki
Owen Hilyard
Daniel Kirichok
David Liu
Thomas Monjalon
Lincoln Lavoie
CI Status
Test Development
Bugzilla Ticket Review
Any Other Business
Intel CI system updates
Need to invite the Intel CI team to the call
Travis CI
No updates
Community Lab
SPDK Build Failures
All 5 systems running SPDK compile testing fully functional.
SPDK Additional Unit Testing
Currently running on the Fedora VM in testing environment
Will be on by this Friday (probably sooner), after testing internally
Move to latest release branch to have more up-to-date commits during testing
Try it because of features that may make it easier to support
May need to fall back to LTS release branches if failures are occurring
Infrastructure Alert
System put in place to notify the team whenever an infrastructure failure occurs due to reliability issues
Broadcom Upgrade to include 100Gbe NICs
Windows mingw-w64 compile testing (Bug-476)
Looking into setting this up and putting it onto the production dashboard
Other Build Services
Cirrus CI
Update on Redhat interns?
Expected on the 30th
OBS
Status of including package spec files in the main repos?
Not quite confident that we will do this
Only real motivation to have this is for OBS
Next steps
What’s missing:
“Jenkins” job to run the pipeline
Something to monitor the result
Juraj to provide some of these quite soon(?)
Maybe submit a pull request to patchwork ci to see where it gets us.
Two systems that are working on getting development set up
Intel dev system with 2 servers
Occasionally borrowing Broadcom system from CI
Basic test cases working, but existing functional tests are not functioning properly
The tests that are passing are likely to be a false positive.
Questions
Is there a way to have TREX run and have a way to expose interfaces (some other way to make Scapy run)
Example on how to make Scapy run properly
Going through existing tests located within DTS
Some tests may be NIC specific; may need to work on scripts to improve coverage
Need to create a progress report in test development so that everybody in the group knows how much work has been done in the DTS team.
Brandon to lead recording the progress of the test development team.
DPDK Community Lab Bug Tracker
New / Updated:
Bug 460 - Broadcom performance testing being setup
Testing fully functional. Reports being sent to patchworks under iol-broadcom-Performance
Bug 466 - Mellanox build errors occur randomly:
Stopping existing TREX processes before starting testing for Mellanox has stopped the failures for quite some time.
Emails submitted to patchwork through the mailing list with “warning” label are labeled as such due to failure of a submodule test. E.g.: SPDK build
Not marked as FAIL because of the lack of failures in the dpdk compile tests.
Next meeting: June 30, 2020
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824