DPDK CI discussions
 help / color / 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, January 29th
Date: Tue, 29 Jan 2019 18:58:20 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78388ED@IRSMSX108.ger.corp.intel.com> (raw)

Red Hat Test Cases:
- We had a separate meeting with Red Hat after our lab meeting today. Aaron and Rashid explained that they have a suite of DPDK tests, some of which use OVS and some of which test DPDK is isolation. These can be easily set up in the DPDK lab.
- We agreed to proceed with this. It's a great way to get additional test coverage which we've been struggling with for a while. Aaron will work with Jeremy on the implementation.
- The initial goal is to get tests running and results into the database. After that, we can decide how to represent the results in the dashboard and patchwork.
- We will need to make sure that running these tests has not impact on the current test cases. The assumption is that current utilization is low enough that this should not be a problem.

DTS Improvements:
- Thomas will solicit community feedback on this. Community help will also be required to implement any changes.

Applying Patches to Sub-Trees:
- Plan is to apply patch sets to master first. If that fails, then we'll use a script to determine which sub-tree to apply the patch set to. Thomas and Ali hope to provide a script this week.
- If a patch set is applied to a sub-tree, then we need to agree whether the baseline for performance comparison should be the master or the sub-tree. Agreed that we should compare to master.

             reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 18:58 O'Driscoll, Tim [this message]
2019-01-29 21:06 ` Jeremy Plsek
2019-01-30  6:43   ` Tu, Lijuan

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26FA93C7ED1EAA44AB77D62FBE1D27BAB78388ED@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=ci@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
	public-inbox-index ci

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox