[dts] [Bug 670] Exception occurs with running nic_single_core_perf with latest DTS version
bugzilla at dpdk.org
bugzilla at dpdk.org
Thu Apr 8 14:22:03 CEST 2021
https://bugs.dpdk.org/show_bug.cgi?id=670
Bug ID: 670
Summary: Exception occurs with running nic_single_core_perf
with latest DTS version
Product: DTS
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: tests
Assignee: dts at dpdk.org
Reporter: alialnu at nvidia.com
Target Milestone: ---
Created attachment 154
--> https://bugs.dpdk.org/attachment.cgi?id=154&action=edit
DTS log with scapy 2.4.4
When running the test 'nic_single_core_perf' on latest DTS version (082321a2
test_plans/vm2vm_virtio_net_perf_test_plan.rst), the following exception
occurs:
"""
File "/path/to/venv/lib/python3.6/site-packages/scapy/packet.py", line 1600,
in getfield_and_val
raise AttributeError(attr)
AttributeError: _offset
"""
Followed by the following exception:
"""
exception.TimeoutException: TIMEOUT on rm -rf x86_64-native-linux-gcc
"""
See full log in attached file.
The previous exceptions happen when using the scapy version defined in
requirements.txt (scapy 2.4.4).
Forcing DTS to use TRex's scapy (2.3.1) causes another exception:
"""
$ PYTHONPATH=/opt/trex-core-2.59/external_libs/scapy-2.3.1/python3 ./dts
module 'scapy.contrib.gtp' has no attribute 'GTPPDUSessionContainer'
No module named 'scapy.contrib.lldp'
No module named 'scapy.contrib.pfcp'
No module named 'scapy.contrib.nsh'
Traceback (most recent call last):
File "./main.py", line 50, in <module>
import dts
File "/path/to/dts/framework/dts.py", line 47, in <module>
from tester import Tester
File "/path/to/dts/framework/tester.py", line 52, in <module>
from packet import SCAPY_IMP_CMD
File "/path/to/dts/framework/packet.py", line 129, in <module>
class scapy(object):
File "/path/to/dts/framework/packet.py", line 144, in scapy
'sctp': SCTP(),
NameError: name 'SCTP' is not defined
"""
Configuration files:
"""
$ cat conf/crbs.cfg
[HOSTNAME]
dut_ip=HOSTNAME
dut_user=root
dut_passwd=
os=linux
dut_arch=
tester_ip=127.0.0.1
tester_passwd=
ixia_group=
pktgen_group=TREX
channels=4
bypass_core0=True
dut_cores=
snapshot_load_side=tester
$ cat conf/nic_single_core_perf.cfg
[suite]
update_expected = True
test_parameters = {'1C/1T': {64: [256], 512: [256]}}
rx_desc_16byte = 'y'
test_duration = 60
accepted_tolerance = 1
expected_throughput = {'ConnectX5_MT4121': {'1C/1T': {64: {256: 0.0}, 512:
{256: 0.0}}}}
$ cat conf/pktgen.cfg
[TREX]
trex_root_path=/opt/trex-core-2.59
trex_lib_path=/opt/trex-core-2.59/automation/trex_control_plane/interactive
config_file=/etc/trex_cfg.yaml
server=127.0.0.1
pcap_file=/opt/trex-core-2.59/stl/sample.pcap
core_num=14
start_trex=yes
$ cat conf/ports.cfg
[HOSTNAME]
ports =
pci=0000:82:00.0,peer=TREX:0;
pci=0000:82:00.1,peer=TREX:1;
$ cat execution.cfg
[Execution1]
crbs=HOSTNAME
drivername=mlx5_core
build_type=meson
test_suites=
nic_single_core_perf,
targets=
x86_64-native-linux-gcc
parameters=nic_type=cfg:perf=true
"""
OS: Ubuntu 18.04.2
Python: 3.6.9
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the dts
mailing list