From: bugzilla@dpdk.org
To: dts@dpdk.org
Subject: [dts] [Bug 670] Exception occurs with running nic_single_core_perf with latest DTS version
Date: Thu, 08 Apr 2021 12:28:59 +0000 [thread overview]
Message-ID: <bug-670-433-ABV1jaqnCY@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-670-433@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=670
--- Comment #2 from Ali Alnubani (alialnu@nvidia.com) ---
The exceptions don't reproduce when updating TRex to v2.87 and running with:
"""
export PYTHONPATH=/opt/trex-core-2.87/external_libs/scapy-2.4.3
./dts
"""
However, I can't update TRex to this version in production due to a regression
unrelated to DTS that I'm facing with it.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-04-08 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 12:22 bugzilla
2021-04-08 12:24 ` bugzilla
2021-04-08 12:28 ` bugzilla [this message]
2021-04-08 12:29 ` [dts] [Bug 670] Exception occurs when " bugzilla
2021-04-08 14:37 ` bugzilla
2021-04-08 15:23 ` bugzilla
2021-04-12 1:54 ` bugzilla
2021-04-14 14:29 ` bugzilla
2021-05-06 14:08 ` bugzilla
2021-06-17 13:08 ` 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-670-433-ABV1jaqnCY@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).