DPDK CI discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, March 26th
Date: Thu, 28 Mar 2019 13:50:01 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB787F0E2@IRSMSX108.ger.corp.intel.com> (raw)

OVS Tests:
- Jeremy and Aaron are still working on setting these up. Expectation is that they'll be running on the temporary hardware by the next meeting.
- Once these are running on the temporary hardware, we'll try running them on the existing vendor hardware.
- The test suite does include some performance tests, but no performance data will be published, only functional test results.
- Testing will be based on the latest DPDK OVS branch that Ian Stokes maintains, with DPDK master.

New Tests:
- Jeremy has created a google doc to capture proposed new tests. It's at: https://docs.google.com/document/d/1WbRoIq0f5SmHM6D5sLbeh7hxRJdE2ppwB5JECHllLjg/edit?usp=sharing.
- Please add proposed new tests to this.
- We'll review and prioritise at the next meeting.
- This can also be used to scope work for a test contractor. Budget for this is available, but we need a clear scope of work before proceeding with this.

Identifying Correct Sub-Tree for Patches:
- Ali's script is running and is working. An updated version should be available soon.

Test Failures:
- Jeremy has been seeing more failures recently, typically compilation errors on next-net. He'll follow up with Ferruh on the details.



             reply	other threads:[~2019-03-28 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 13:50 O'Driscoll, Tim [this message]
2019-04-03 20:49 ` Thomas Monjalon
2019-04-08 13:34   ` O'Driscoll, Tim

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=26FA93C7ED1EAA44AB77D62FBE1D27BAB787F0E2@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).