From: bugzilla@dpdk.org
To: dts@dpdk.org
Subject: [dts] [Bug 640] Modify the test nic_single_core_perf so that the accepted tolerance is a percentage
Date: Mon, 22 Feb 2021 16:56:54 +0000 [thread overview]
Message-ID: <bug-640-433@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=640
Bug ID: 640
Summary: Modify the test nic_single_core_perf so that the
accepted tolerance is a percentage
Product: DTS
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: tests
Assignee: dts@dpdk.org
Reporter: alialnu@nvidia.com
Target Milestone: ---
An iteration/case in the test nic_single_core_perf currently fails if the delta
(difference between real rx_pps and expected rx_pps) exceeds the absolute
number specified by 'accepted_tolerance' in conf/nic_single_core_perf.cfg.
The default 'accepted_tolerance' is set to 1 mpps, which is very large when the
expected is only a few million packets per second, specially for large frame
sizes.
Since test results are now reported to the mailing list in percentages, I
suggest updating the test so that the accepted tolerance is a percentage rather
than an absolute number.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-04-01 11:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-640-433@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).