[dpdk-ci] Intel performance test is failing

[Chen, Zhaoyan]

Hi, Jeremy and Lincoln,

Did you change anything on the Intel testbed? DTS code or testbed environment?
And could you send me the detailed test logs? We will do a quick check.

Thanks


Regards,
Zhaoyan Chen

From: Lincoln Lavoie <lylavoie at iol.unh.edu>
Sent: Friday, January 24, 2020 4:29 AM
To: Jeremy Plsek <jplsek at iol.unh.edu>
Cc: Thomas Monjalon <thomas at monjalon.net>; ci at dpdk.org; Tu, Lijuan <lijuan.tu at intel.com>; Chen, Zhaoyan <zhaoyan.chen at intel.com>; Xu, Qian Q <qian.q.xu at intel.com>
Subject: Re: [dpdk-ci] Intel performance test is failing

In the "off cases," is that specific to that hardware, or does it happen on all hardware variants from time-to-time?

On Thu, Jan 23, 2020 at 11:25 AM Jeremy Plsek <jplsek at iol.unh.edu<mailto:jplsek at iol.unh.edu>> wrote:
On Thu, Jan 23, 2020 at 11:06 AM Thomas Monjalon <thomas at monjalon.net<mailto:thomas at monjalon.net>> wrote:
>
> Hi,
>
> The test iol-intel-Performance is failing on all patches
> for a couple of days.
> It seems to be due to a perf drop with a 10G device
>
> Can we disable this test until we understand what happens?
>
> We need also to understand how to avoid such failure,
> and how to monitor and disable it faster.
>
> Thanks
>
>
Hi Thomas,

I've disabled it for now until someone from the Intel team can look
into it (cc'd).

I've also seem problems where the results are completely off
(-15mpps), and I've been rerunning those when they happen. I'm hoping
those can be resolved too.

--
Jeremy Plsek
UNH InterOperability Laboratory


--
Lincoln Lavoie
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie at iol.unh.edu<mailto:lylavoie at iol.unh.edu>
https://www.iol.unh.edu
+1-603-674-2755 (m)
[http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png]<https://www.iol.unh.edu/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/ci/attachments/20200131/bc1c4e31/attachment.html>