From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: dpdklab <dpdklab@iol.unh.edu>,
ci@dpdk.org, dts@dpdk.org, Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-ci] Failures for nic_single_core test
Date: Wed, 30 Jun 2021 11:55:57 -0400 [thread overview]
Message-ID: <CAOE1vsPg01gLe155PSrKrJOwGBv9cKQPPEwt1WRjiVO1VKFr6A@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8xKACdKGaFDkj=H7gKCNcKVUW17x00+rKU8jT+XnLqtmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
Hi David,
We're looking into this. We think it is related to a baseline change /
issue, when we rolled out fixes, because DTS made some changes to how it
lists results for cores / threads. Owen can give some more details. Once
we track it down, we'll rerun the failed cases.
Cheers,
Lincoln
On Wed, Jun 30, 2021 at 11:37 AM David Marchand <david.marchand@redhat.com>
wrote:
> Hello guys,
>
> Since 06/28, I see the nic_single_core test failing most of the time
> with the system hosting the i40e nic.
> I suspect this has something to do with a recent change with reporting
> performance difference in DTS, could you have a look and confirm?
>
>
> --
> David Marchand
>
>
--
*Lincoln Lavoie*
Principal 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: 2115 bytes --]
prev parent reply other threads:[~2021-06-30 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 15:37 David Marchand
2021-06-30 15:55 ` 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=CAOE1vsPg01gLe155PSrKrJOwGBv9cKQPPEwt1WRjiVO1VKFr6A@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dpdklab@iol.unh.edu \
--cc=dts@dpdk.org \
/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).