From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 122] Performance results are not correct on Intel I40E environments
Date: Tue, 11 Dec 2018 20:34:22 +0000 [thread overview]
Message-ID: <bug-122-149-wI3z1YhqOd@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-122-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=122
--- Comment #1 from Jeremy Plsek (jplsek@iol.unh.edu) ---
I ran this manually, and it had passing results for me.
This is how I tested it (after stopping the CI from running on the node
temporarily):
In one terminal:
cd /root/test_harness/trex-core-2.26/scripts
./t-rex-64 -i --no-scapy-server --cfg ../../trex_cfg.yaml
In another terminal:
cd /root/test_harness/dts
./dts -s --snapshot /tmp/dpdktest2/dpdk.tar.gz # tarball with the patch applied
using commit b0aa225b45 as a baseline for the expected results from
conf/nic_single_core_perf.cfg
Then looking at the output folder logs, it had similar results to the email.
How did you test this? What baseline did you use? How did you make the tarball
that was being tested?
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2018-12-11 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-122-149@http.bugs.dpdk.org/>
2018-12-11 20:34 ` bugzilla [this message]
2018-12-12 3:28 ` bugzilla
2018-12-12 15:48 ` bugzilla
2020-04-21 13:47 ` bugzilla
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-122-149-wI3z1YhqOd@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@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).