From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>
Cc: 'Bob Noseworthy' <ren@iol.unh.edu>,
"Mcnamara, John" <john.mcnamara@intel.com>,
'Shepard Siegel' <shepard.siegel@atomicrules.com>,
'Thomas Monjalon' <thomas@monjalon.net>,
'Erez Scop' <erezsc@mellanox.com>,
'Shreyansh Jain' <shreyansh.jain@nxp.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"'pmacarth@iol.unh.edu'" <pmacarth@iol.unh.edu>,
'Matt Spencer' <Matt.Spencer@arm.com>,
'George Zhao' <George.Y.Zhao@huawei.com>,
"'Mishra, Shishir'" <Shishir.Mishra@spirent.com>,
'Lixuming' <lixuming@huawei.com>,
"Tkachuk, Georgii" <georgii.tkachuk@intel.com>,
'Trishan de Lanerolle' <tdelanerolle@linuxfoundation.org>,
'Sean Campbell' <scampbel@qti.qualcomm.com>,
'Ali Alnubani' <alialnu@mellanox.com>,
"'May Chen'" <May.Chen@huawei.com>,
"'Lodha, Nishant'" <Nishant.Lodha@cavium.com>,
"Zhang, Chun" <chun.zhang@intel.com>,
"'Malla, Malathi'" <Malathi.Malla@spirent.com>,
'khemendra kumar' <khemendra.kumar13@gmail.com>,
"'graeme.gregory@linaro.org'" <graeme.gregory@linaro.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"Wang, Liang-min" <liang-min.wang@intel.com>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, August 14th
Date: Thu, 16 Aug 2018 10:40:42 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB7742422@IRSMSX107.ger.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Test Results:
* Some tests are showing potential failures when they shouldn't be. Lijuan will investigate the root cause for the Intel 10G failures. Ali will check on the Mellanox results.
* Jeremy has added Intel legal disclaimers to the bottom of the results page. Erez will check whether similar disclaimers are required for Mellanox. I'll discuss with Trishan to see if the LF legal team are able to discuss a common set of disclaimers with the various vendor legal teams.
* Discussed what we should do if test results show a failure but we don't believe there's a real issue. Jeremy will look into adding a button to re-run tests on demand.
Misc:
* One of our DPDK validation team will be on assignment close to UNH for 3-4 weeks. Larry (Liang-Min Wang) will work with the UNH team to arrange a date for a visit to the lab while.
* UNH received a request for a database dump instead of accessing information via the REST API. Agreed that the highest priority is confidentiality of vendor data. UNH will investigate if the request can be satisfied while preserving confidentiality. If not, then the REST API will need to be used.
[-- Attachment #2: Type: text/html, Size: 3498 bytes --]
reply other threads:[~2018-08-16 10:40 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=26FA93C7ED1EAA44AB77D62FBE1D27BAB7742422@IRSMSX107.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=George.Y.Zhao@huawei.com \
--cc=Malathi.Malla@spirent.com \
--cc=Matt.Spencer@arm.com \
--cc=May.Chen@huawei.com \
--cc=Nishant.Lodha@cavium.com \
--cc=Shishir.Mishra@spirent.com \
--cc=alialnu@mellanox.com \
--cc=chun.zhang@intel.com \
--cc=ci@dpdk.org \
--cc=erezsc@mellanox.com \
--cc=ferruh.yigit@intel.com \
--cc=georgii.tkachuk@intel.com \
--cc=graeme.gregory@linaro.org \
--cc=john.mcnamara@intel.com \
--cc=khemendra.kumar13@gmail.com \
--cc=liang-min.wang@intel.com \
--cc=lijuan.tu@intel.com \
--cc=lixuming@huawei.com \
--cc=pmacarth@iol.unh.edu \
--cc=qian.q.xu@intel.com \
--cc=ren@iol.unh.edu \
--cc=scampbel@qti.qualcomm.com \
--cc=shepard.siegel@atomicrules.com \
--cc=shreyansh.jain@nxp.com \
--cc=tdelanerolle@linuxfoundation.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).