From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: "Xia, Chenbo" <chenbo.xia@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "Fu, Patrick" <patrick.fu@intel.com>
Subject: Re: [dpdk-ci] CI errors on mellanox-Performance
Date: Fri, 17 Jul 2020 09:01:58 -0400 [thread overview]
Message-ID: <CAOE1vsNFt_c7kbj_KNMmW5sN1W9t9abN4fL+mzBp3Fo4CzypVw@mail.gmail.com> (raw)
In-Reply-To: <MN2PR11MB4063D60EAE9CAAB3E596D9599C7C0@MN2PR11MB4063.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
It looks like the test ran correctly, and the failures are caused by the
performance change of more than 1%. The Mellanox team would need to comment
on the requirement, as each vendor establishes their expected baseline and
allowed performance change.
Cheers,
Lincoln
On Thu, Jul 16, 2020 at 11:15 PM Xia, Chenbo <chenbo.xia@intel.com> wrote:
> Hi,
>
>
>
> There’s some CI errors on Mellanox-Performance:
>
>
>
> http://mails.dpdk.org/archives/test-report/2020-July/144853.html
>
> http://mails.dpdk.org/archives/test-report/2020-July/144880.html
>
>
>
> I think these patches are not related to this test.
>
>
>
> Could someone check the issue?
>
>
>
> Best regards,
>
> Chenbo (Troy)
>
>
>
--
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu/>
[-- Attachment #2: Type: text/html, Size: 2761 bytes --]
prev parent reply other threads:[~2020-07-17 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 3:15 Xia, Chenbo
2020-07-17 13:01 ` Lincoln Lavoie [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=CAOE1vsNFt_c7kbj_KNMmW5sN1W9t9abN4fL+mzBp3Fo4CzypVw@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=chenbo.xia@intel.com \
--cc=ci@dpdk.org \
--cc=patrick.fu@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).