From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday July 16th
Date: Thu, 18 Jul 2019 13:21:22 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78FEC2C@IRSMSX108.ger.corp.intel.com> (raw)
New hardware:
- NXP HW has been set up and handed off to NXP.
- Broadcom HW has been set up and handed off to Broadcom. They're now focusing on getting DTS working.
OVS tests:
- Running continuously now on master, but seeing issues. On one system, getting segfaults from OVS. May be due to out of data OS. Other system having problems with crashes during OVS performance tests. Jeremy is working with Aaron on this.
SPDK tests:
- Goal is similar to OVS - identify any impacts on SPDK due to new DPDK patches.
- Initial focus is on compilation testing for OSs not already covered by DPDK CI (e.g. FreeBSD). System is set up and Jeremy is working with the SPDK team to debug issues.
- After that, next priority is e DPDK unit tests for memory allocation and PCI hotplug.
- Darek and Zhaoyan will discuss offline to see if this testing can be included with internal Intel CI.
Windows testing:
- Thomas requested Windows testing previously. This is already enabled in Intel compilation testing.
Mellanox test failures:
- There are some failures for performance tests on Mellanox. Not sure if this is related to new OVS tests. Jeremy will add manual check to make sure TRex is not still running after the OVS tests.
UNH Priority Order:
1. Finish setup of OVS tests
2. New hardware setup (NXP & Broadcom). Initial UNH setup is complete so this should mostly be covered by vendors now.
3. Compilation testing
4. Unit testing
next reply other threads:[~2019-07-18 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 13:21 O'Driscoll, Tim [this message]
2019-08-13 12:31 ` [dpdk-ci] Atomic Rules on DPDK Lab call today Shepard Siegel
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=26FA93C7ED1EAA44AB77D62FBE1D27BAB78FEC2C@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=ci@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).