DPDK CI discussions
 help / color / mirror / Atom feed
From: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
To: Brandon Lo <blo@iol.unh.edu>, David Marchand <david.marchand@redhat.com>
Cc: "dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>,
	Thomas Monjalon <thomas@monjalon.net>,
	"ci@dpdk.org" <ci@dpdk.org>, "Tu, Lijuan" <lijuan.tu@intel.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-ci] [dpdklab] Re:  Intel performance test is failing
Date: Wed, 11 Mar 2020 02:13:21 +0000	[thread overview]
Message-ID: <9DEEADBC57E43F4DA73B571777FECECA41EFB9C5@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAOeXdvZ_Jp_xM+crx+XgHrBhscJwEkdHStKVHdhBf9jVchSrBg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

Hi, Brandon,

Yes, it’s a wired issue. And it also mixed our DTS upgrading and Trex upgrading.
So we are reviewing our DTS script, different Trex version, and CI calling procedure.

Anyway, we are focusing on this task recently, any update will let you know.

Thanks.

Regards,
Zhaoyan Chen

From: Brandon Lo <blo@iol.unh.edu>
Sent: Tuesday, March 10, 2020 10:46 PM
To: David Marchand <david.marchand@redhat.com>
Cc: Chen, Zhaoyan <zhaoyan.chen@intel.com>; dpdklab@iol.unh.edu; Lincoln Lavoie <lylavoie@iol.unh.edu>; Thomas Monjalon <thomas@monjalon.net>; ci@dpdk.org; Tu, Lijuan <lijuan.tu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>
Subject: Re: [dpdklab] Re: [dpdk-ci] Intel performance test is failing

Hi Zhaoyan,

How is the current status of the Intel 82599ES?
Were there any configuration changes made to fix performance issues?

Thanks

On Tue, Mar 10, 2020 at 9:11 AM Brandon Lo <blo@iol.unh.edu<mailto:blo@iol.unh.edu>> wrote:
Hi David,

This was just a weird issue with the packet generator not cleaning itself after a test fast enough before another test.
I'll rerun the tests that were affected and keep an eye out to see if it's stable enough to be put back online.

Thanks

On Tue, Mar 10, 2020 at 5:33 AM David Marchand <david.marchand@redhat.com<mailto:david.marchand@redhat.com>> wrote:
On Tue, Mar 3, 2020 at 3:14 PM Brandon Lo <blo@iol.unh.edu<mailto:blo@iol.unh.edu>> wrote:
>
> Hi David and Zhaoyan,
>
>
> Yes, those results are related to the Intel machine; I have disabled testing for the Intel testbed.
>
> The 82599ES machine is now available for ssh and modifications.

Any news about this?

I received a failure on a patch of mine (changing macros in a ARM header).
https://lab.dpdk.org/results/dashboard/patchsets/9900/

But this time, it is with the 40G Intel nic test.

--
David Marchand


--

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu<mailto:blo@iol.unh.edu>

www.iol.unh.edu<http://www.iol.unh.edu/>


--

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu<mailto:blo@iol.unh.edu>

www.iol.unh.edu<http://www.iol.unh.edu/>

[-- Attachment #2: Type: text/html, Size: 9792 bytes --]

  reply	other threads:[~2020-03-11  2:13 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 15:58 [dpdk-ci] " Thomas Monjalon
2020-01-23 16:25 ` Jeremy Plsek
2020-01-23 20:28   ` Lincoln Lavoie
2020-01-31  3:17     ` Chen, Zhaoyan
2020-01-31 14:48       ` Jeremy Plsek
2020-02-03  3:57         ` Chen, Zhaoyan
2020-03-03  9:21           ` David Marchand
2020-03-03 14:13             ` [dpdk-ci] [dpdklab] " Brandon Lo
2020-03-10  9:32               ` David Marchand
2020-03-10 13:11                 ` Brandon Lo
2020-03-10 14:46                   ` Brandon Lo
2020-03-11  2:13                     ` Chen, Zhaoyan [this message]
2020-03-17 19:34                       ` Brandon Lo
2020-03-18 13:04                         ` Chen, Zhaoyan
2020-03-20  1:35                           ` Chen, Zhaoyan
2020-03-20 17:48                             ` Brandon Lo
2020-03-23  1:58                               ` Chen, Zhaoyan
2020-03-24 13:30                                 ` Brandon Lo
2020-03-25  4:59                                   ` Chen, Zhaoyan
2020-03-26 15:39                                     ` Brandon Lo
2020-03-30  4:43                                       ` Chen, Zhaoyan
2020-03-31 13:42                                         ` Brandon Lo
2020-04-01  6:00                                           ` Ma, LihongX
2020-04-02 18:39                                             ` Brandon Lo
2020-04-03  1:14                                               ` Ma, LihongX
2020-04-15  9:39                                               ` Ma, LihongX
2020-04-15 19:30                                                 ` Brandon Lo
2020-04-16  3:40                                                   ` Ma, LihongX
2020-04-16 15:04                                                     ` Brandon Lo
2020-04-17  1:54                                                       ` Ma, LihongX
2020-04-17  7:00                                                       ` Ma, LihongX
2020-04-17 15:52                                                         ` Brandon Lo
2020-04-18  1:13                                                           ` Ma, LihongX
2020-04-28  3:39                                               ` Ma, LihongX
2020-04-28 16:51                                                 ` Brandon Lo
2020-04-29  5:30                                                   ` Ma, LihongX
2020-04-30 14:19                                                     ` Brandon Lo
2020-05-06 13:05                                                       ` Brandon Lo
2020-05-08  8:02                                                         ` Ma, LihongX
2020-05-12  5:41                                                         ` Ma, LihongX
2020-05-14 16:12                                                           ` Brandon Lo
2020-05-15  1:30                                                             ` Ma, LihongX

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=9DEEADBC57E43F4DA73B571777FECECA41EFB9C5@SHSMSX104.ccr.corp.intel.com \
    --to=zhaoyan.chen@intel.com \
    --cc=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=qian.q.xu@intel.com \
    --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).