DPDK CI discussions
 help / color / 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
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 --]

<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi All,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">If issues come up while Jeremy is out, please email <a href="mailto:dpdklab@iol.unh.edu">dpdklab@iol.unh.edu</a>, and this will reflect to our team, so things can be resolved as quickly as possible.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Cheers,<br>Lincoln</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 21, 2019 at 9:23 AM O&#39;Driscoll, Tim &lt;<a href="mailto:tim.odriscoll@intel.com">tim.odriscoll@intel.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">OVS Tests:<br>
- Tests are running on Intel machines. Mellanox setup is in progress.<br>
- 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.<br>
- 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.<br>
- 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.<br>
<br>
SPDK Tests:<br>
- 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.<br>
- I&#39;ll connect the SPDK team with Jeremy and Lincoln to discuss further.<br>
<br>
Misc:<br>
- Jeremy is on vacation for the next 2.5 weeks. UNH will have coverage to deal with support issues.<br>
- I&#39;ll cancel the next meeting.<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b>Lincoln Lavoie</b><br></div><div>Senior Engineer, Broadband Technologies</div><div>21 Madbury Rd., Ste. 100, Durham, NH 03824</div><div><a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a></div><div><a href="https://www.iol.unh.edu" target="_blank">https://www.iol.unh.edu</a></div><div>+1-603-674-2755 (m)<br></div><div><a href="https://www.iol.unh.edu/" target="_blank"><img src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png"></a></div></div></div></div></div></div></div></div></div></div></div></div>

  reply index

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 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=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

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