DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 21st
Date: Tue, 21 May 2019 09:27:59 -0400	[thread overview]
Message-ID: <CAOE1vsOQbKu8zmfBiBMZ-TNVT3O_yv-KZxHNfHwrx5ZRTK-phg@mail.gmail.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78BC5A0@IRSMSX108.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

Hi All,

If issues come up while Jeremy is out, please email dpdklab@iol.unh.edu,
and this will reflect to our team, so things can be resolved as quickly as
possible.

Cheers,
Lincoln

On Tue, May 21, 2019 at 9:23 AM O'Driscoll, Tim <tim.odriscoll@intel.com>
wrote:

> 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. 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.
> - 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.
>
> Misc:
> - Jeremy is on vacation for the next 2.5 weeks. UNH will have coverage to
> deal with support issues.
> - I'll cancel the next meeting.
>
>
>
>
>
>

-- 
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu/>

[-- Attachment #2: Type: text/html, Size: 2720 bytes --]

  reply	other threads:[~2019-05-21 13:27 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 [this message]
2019-05-21 14:28 ` Thomas Monjalon

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=CAOE1vsOQbKu8zmfBiBMZ-TNVT3O_yv-KZxHNfHwrx5ZRTK-phg@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --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).