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>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, July 17th
Date: Thu, 19 Jul 2018 14:54:37 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB7721682@IRSMSX107.ger.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
UNH Policies and Procedures Doc:
Document is available at: https://docs.google.com/document/d/1rtSwpNKltVNyDKNWgeTV5gaYeDoAPlK-sfm8XE7o_5s/edit?usp=sharing
I reviewed it and it looks good to me.
Please add any comments to the google doc, or send them directly to Bob (ren@iol.unh.edu<mailto:ren@iol.unh.edu>).
Dashboard:
Dashboard is in much better shape now and most tests are passing.
We do need to monitor the results and determine if the tolerance is right. If it's too high then all tests will pass and we'll miss any genuine issues. If it's too low then we'll have too many tests failing when there isn't really a problem. Agreed that tuning the tolerance is the responsibility of each vendor.
For Intel, we need to add the specific test config to the results page. We need to confirm the config details to Patrick, and he'll add this to the results pages. Other vendors may want to do something similar.
Hardware:
Shreyansh is almost ready to ship the NXP hardware. It should be in UNH in 2-3 weeks.
[-- Attachment #2: Type: text/html, Size: 5952 bytes --]
next reply other threads:[~2018-07-19 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 14:54 O'Driscoll, Tim [this message]
2018-08-16 9:33 ` Yigit, Ferruh
2018-08-16 19:58 ` Jeremy Plsek
2018-08-17 16:30 ` Yigit, Ferruh
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=26FA93C7ED1EAA44AB77D62FBE1D27BAB7721682@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=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).