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] DPDK Community Lab Meeting Minutes, Tuesday August 13th
Date: Tue, 13 Aug 2019 14:25:24 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB791A0BD@IRSMSX108.ger.corp.intel.com> (raw)

New hardware:
- NXP and Broadcom hardware has been set up and handed off to the vendors. They're now focusing on getting DTS working and performance optimized.
- Atomic Rules are interested in engaging again. Shep will follow up with UNH offline on the details.

Compile tests:
- Compile testing has been added on master for 2 OSs (FreeBSD and Ubuntu). More OSs will be added over time.
- Compile tests for OVS-DPDK have also been added.
- We need to look at how to handle compile failures for OVS-DPDK (and SPDK in future). Should these tests be enabled per patch set so that patch authors know immediately if their patches break downstream projects? We'll discuss again at a future meeting when some of the maintainers (Thomas, Ferruh) are available.

OVS tests:
- Tests have been set up on Intel and Mellanox systems. Tests will be run when master is updated. Email notification will be sent if there are failures. Results will be shown on the dashboard under the tarballs page.

SPDK tests:
- Will be added similar to OVS. Initially this will just include compile testing. The SPDK team will then identify additional tests that need to be run.

Unit tests:
- Updates to the fast test suite have been completed. Should be OK to run in UNH now. Jeremy will look into this.
- Ideally want to turn on all unit tests except the perf unit tests (these are too long to run). Work is underway on cleanup of the other unit tests.


                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:
  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=26FA93C7ED1EAA44AB77D62FBE1D27BAB791A0BD@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

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 \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


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