DPDK CI discussions
 help / color / Atom feed
* [dpdk-ci] Minutes of DPDK Lab Meeting, August 14th
@ 2018-08-16 10:40 O'Driscoll, Tim
  0 siblings, 0 replies; only message in thread
From: O'Driscoll, Tim @ 2018-08-16 10:40 UTC (permalink / raw)
  To: ci
  Cc: Bob Noseworthy, Mcnamara, John, Shepard Siegel, Thomas Monjalon,
	Erez Scop, Shreyansh Jain, Xu, Qian Q, pmacarth, Matt Spencer,
	George Zhao, Mishra, Shishir, Lixuming, Tkachuk, Georgii,
	Trishan de Lanerolle, Sean Campbell, Ali Alnubani, May Chen,
	Lodha, Nishant, Zhang, Chun, Malla, Malathi, khemendra kumar,
	graeme.gregory, Yigit, Ferruh, Tu, Lijuan, Wang, Liang-min

[-- 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 --]

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">Test Results:<o:p></o:p></p>
<p class="MsoPlainText">&#8226; Some tests are showing potential failures when they shouldn&#8217;t be. Lijuan will investigate the root cause for the Intel 10G failures. Ali will check on the Mellanox results.<o:p></o:p></p>
<p class="MsoPlainText">* Jeremy has added Intel legal disclaimers to the bottom of the results page. Erez will check whether similar disclaimers are required for Mellanox. I&#8217;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.<o:p></o:p></p>
<p class="MsoPlainText">* Discussed what we should do if test results show a failure but we don&#8217;t believe there&#8217;s a real issue. Jeremy will look into adding a button to re-run tests on demand.<o:p></o:p></p>
<p class="MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class="MsoPlainText">Misc:<o:p></o:p></p>
<p class="MsoPlainText">* 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.<o:p></o:p></p>
<p class="MsoPlainText">* 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.<o:p></o:p></p>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-08-16 10:40 [dpdk-ci] Minutes of DPDK Lab Meeting, August 14th O'Driscoll, Tim

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