From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, March 26th
Date: Mon, 8 Apr 2019 13:34:25 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78919C1@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <4343874.ifZTGfLS2i@xps>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Wednesday, April 3, 2019 9:50 PM
> To: ci@dpdk.org
> Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>
> Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, March 26th
>
> 28/03/2019 14:50, O'Driscoll, Tim:
> > - Jeremy has created a google doc to capture proposed new tests. It's
> at:
> https://docs.google.com/document/d/1WbRoIq0f5SmHM6D5sLbeh7hxRJdE2ppwB5J
> ECHllLjg/edit?usp=sharing.
> > - Please add proposed new tests to this.
>
> My proposals (added in the doc):
>
> - Compilation with coverage for Arm/Intel 32/64 and
> Linux/FreeBSD/Windows
> with make/meson and gcc/clang
> Not HW dependent (cross-compilation for Arm)
> The matrix can be big if testing several distros, etc.
> - Unit tests
> dependent on CPU arch
I added some suggestions as well - performance tests for vhost/virtio, crypto and compression.
We should discuss the priorities at tomorrow's meeting, so if others have inputs please add them before then.
>
> About non-HW dependent testing, I think we can share the workload of
> such test
> across all machines.
prev parent reply other threads:[~2019-04-08 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 13:50 O'Driscoll, Tim
2019-04-03 20:49 ` Thomas Monjalon
2019-04-08 13:34 ` O'Driscoll, Tim [this message]
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=26FA93C7ED1EAA44AB77D62FBE1D27BAB78919C1@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=ci@dpdk.org \
--cc=thomas@monjalon.net \
/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).