DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: David Marchand <david.marchand@redhat.com>,
	"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>,
	 "Ma, LihongX" <lihongx.ma@intel.com>,
	"Zhang, XuemingX" <xuemingx.zhang@intel.com>
Subject: Re: [dpdk-ci] [dpdklab] Re:  Intel performance test is failing
Date: Fri, 20 Mar 2020 13:48:40 -0400	[thread overview]
Message-ID: <CAOeXdvbUinBw0Gep4hzTPBTjMkeQMbk6EJY1ktp++Kcru815ZQ@mail.gmail.com> (raw)
In-Reply-To: <9DEEADBC57E43F4DA73B571777FECECA41F025A1@SHSMSX104.ccr.corp.intel.com>

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

Hi Zhaoyan,

Currently, the 40G machine is stable enough to be put on production
dashboard to run tests which may cause Trex to be killed.
Should I disable the 40G Intel machine for you to make changes?

Also, just for confirmation: on the 10G machine, is the folder that you are
using for the testing located in */opt/test-harness/dts-2020-3-4, o*r are
you still using the one in the standard */opt/test-harness/dts* folder?

If everything is ok, I will enable the 10G machine for production testing.

Thank you very much

On Thu, Mar 19, 2020 at 9:36 PM Chen, Zhaoyan <zhaoyan.chen@intel.com>
wrote:

> Brandon,
>
>
>
> We worked out a workaround on Intel testbeds. NNT(10G) and FVL(40G). Could
> you please help to recover them?
>
>
>
> But, for FVL(40G) testbed,  we met some problems, could you please help to
> check before recover it
>
>    - Sometime 1G hugepage will be changed to 2Mhugepage
>    automatically...we have to restart the system
>    - When we debugging on the testbed, found that Trex was killed by some
>    one(app)..
>
> Please help to check if any other program running on the testbed.
>
>
>
> Thanks a lot.
>
>
>
>
>
>
>
> *Regards,*
>
> *Zhaoyan Chen*
>
>
>
> *From:* Chen, Zhaoyan <zhaoyan.chen@intel.com>
> *Sent:* Wednesday, March 18, 2020 9:04 PM
> *To:* Brandon Lo <blo@iol.unh.edu>
> *Cc:* David Marchand <david.marchand@redhat.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>; Chen, Zhaoyan <zhaoyan.chen@intel.com>
> *Subject:* RE: [dpdklab] Re: [dpdk-ci] Intel performance test is failing
>
>
>
> Brandon, we almost made a workaround.
>
>
>
> Maybe tomorrow, you could recover Intel’s testbed. I will let you know
> soon.
>
>
>
>
>
>
>
> *Regards,*
>
> *Zhaoyan Chen*
>
>
>
> *From:* Brandon Lo <blo@iol.unh.edu>
> *Sent:* Wednesday, March 18, 2020 3:34 AM
> *To:* Chen, Zhaoyan <zhaoyan.chen@intel.com>
> *Cc:* David Marchand <david.marchand@redhat.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,
>
>
>
> Have you finished making changes on the Intel machine?
>
> I will turn on the machine on March 3rd for testing if you do not have any
> issues with it.
>
> Please let me know if you need anything else.
>
>
>
> Thanks
>
>
>
> On Tue, Mar 10, 2020 at 10:13 PM Chen, Zhaoyan <zhaoyan.chen@intel.com>
> wrote:
>
> 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> 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>
> wrote:
>
> On Tue, Mar 3, 2020 at 3:14 PM Brandon Lo <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
>
> www.iol.unh.edu
>
>
>
>
> --
>
> Brandon Lo
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> blo@iol.unh.edu
>
> www.iol.unh.edu
>
>
>
>
> --
>
> Brandon Lo
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> blo@iol.unh.edu
>
> www.iol.unh.edu
>


-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

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

  reply	other threads:[~2020-03-20 17:49 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
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 [this message]
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=CAOeXdvbUinBw0Gep4hzTPBTjMkeQMbk6EJY1ktp++Kcru815ZQ@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=lihongx.ma@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=qian.q.xu@intel.com \
    --cc=thomas@monjalon.net \
    --cc=xuemingx.zhang@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /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).