DPDK CI discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>, Ruoshan Shi <ruoshan.shi@nxp.com>,
	Rajan Gupta <rajan.gupta@nxp.com>
Subject: Re: [dpdk-ci] NXP performance stability issue
Date: Tue, 21 Apr 2020 13:51:19 +0000	[thread overview]
Message-ID: <AM6PR04MB445659056D8FD9A4759CC5FC89D50@AM6PR04MB4456.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <2477674.BddDVKsqQX@thomas>

Thanks! We will look into it at high priority.

Regards,
Hemant

> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Tuesday, April 21, 2020 7:16 PM
> To: Lincoln Lavoie <lylavoie@iol.unh.edu>
> Cc: ci@dpdk.org
> Subject: [dpdk-ci] NXP performance stability issue
> 
> Hi, following our meeting,
> this is the link to the patch with NXP failure we discussed:
> 	https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2F
> patches.dpdk.org%2Fpatch%2F69007%2F&amp;data=02%7C01%7Chemant.ag
> rawal%40nxp.com%7C85e832d728f54140481a08d7e5fa46bc%7C686ea1d3bc
> 2b4c6fa92cd99c5c301635%7C0%7C0%7C637230735404194974&amp;sdata=
> mzgTGo%2FgXH5HPK5eVXpWv4H36WnqlPpCFRsdMNQoFoc%3D&amp;reserv
> ed=0
> 
> Lincoln, thank you for opening bugzilla tickets for:
> 	- NXP investigation (high priority)
> 	- stability mitigation (standard priority) Mitigation can be doing
> multiple runs and/or taking external parameters into account.
> 


      reply	other threads:[~2020-04-21 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:45 Thomas Monjalon
2020-04-21 13:51 ` Hemant Agrawal [this message]

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=AM6PR04MB445659056D8FD9A4759CC5FC89D50@AM6PR04MB4456.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=ci@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=rajan.gupta@nxp.com \
    --cc=ruoshan.shi@nxp.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).