From: Thomas Monjalon <thomas@monjalon.net>
To: ci@dpdk.org
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 21st
Date: Tue, 21 May 2019 16:28:56 +0200 [thread overview]
Message-ID: <5547763.pTxsDfsT3u@xps> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78BC5A0@IRSMSX108.ger.corp.intel.com>
21/05/2019 15:23, O'Driscoll, Tim:
> OVS Tests:
> - Tests are running on Intel machines. Mellanox setup is in progress.
> - Tests are run whenever DPDK master is updated, not per patch set, because the tests take ~4 hours.
It defeats the initial goal of avoiding breaks.
Why is it taking to long?
Can we have a shorter test?
> Testing is against the DPDK latest branch in OVS.
> - Test results are in the dashboard under the tarballs tab. Once the test setup is complete, we can look at how to make these more readable/more visible.
It would be more visible if test is per patchset, integrated in patchwork.
> - At the moment, test results go to the DPDK patchwork mailing list. We need to look at how to include OVS maintainers in the distribution.
>
> SPDK Tests:
> - The SPDK team are interested in contributing tests, similar to OVS. This would allow them to identify any compatibility issues earlier, and would give us increased test coverage for DPDK.
> - I'll connect the SPDK team with Jeremy and Lincoln to discuss further.
Please ask them to prepare a short test.
prev parent reply other threads:[~2019-05-21 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 13:23 O'Driscoll, Tim
2019-05-21 13:27 ` Lincoln Lavoie
2019-05-21 14:28 ` Thomas Monjalon [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=5547763.pTxsDfsT3u@xps \
--to=thomas@monjalon.net \
--cc=ci@dpdk.org \
--cc=tim.odriscoll@intel.com \
/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).