From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Cc: David Marchand <david.marchand@6wind.com>
Subject: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday June 18st
Date: Tue, 18 Jun 2019 14:35:25 +0100 [thread overview]
Message-ID: <408f2224-544a-10f6-4cfd-3be240e0c0b2@intel.com> (raw)
Tim was out, we did a quick status update and closed early
OVS Tests:
- Work is going on.
SPDK Tests:
- Need to investigate
CI work:
- Will stat next week probably
- Zhaoyan and Aaron already has experience on the topic
Unit test:
- Aaron is working to run unit test on travis
- David Marchand has a patchset in mail list for unit test fixes
- Needs review on the patchset, Aaron's feedback is positive
Misc:
- Aaron did an update to associate travis builds with patchset
- Can it be possible to send a status to patchwork from travis?
- New vendor infrastructure work from past going on.
reply other threads:[~2019-06-18 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=408f2224-544a-10f6-4cfd-3be240e0c0b2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@6wind.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).