Bug 833

Summary:	link_bonding_autotest fails on subsequent runs
Product:	DPDK	Reporter:	Konstantin Ananyev (konstantin.v.ananyev)
Component:	other	Assignee:	Konstantin Ananyev (konstantin.v.ananyev)
Status:	UNCONFIRMED ---
Severity:	minor	CC:	3chas3, aconole, ajit.khaparde
Priority:	Normal
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All

Description Konstantin Ananyev 2021-10-22 15:33:42 CEST

Comment 1 Konstantin Ananyev 2021-10-22 15:38:22 CEST

./dpdk.org/x86_64-native-linuxapp-gcc-meson/app/test/dpdk-test --lcores=6-8 -n 4 --no-pci
first run is ok:
RTE>>link_bonding_autotest
....
+ ------------------------------------------------------- +
 + Test Suite Summary : Link Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + Tests Total :       65
 + Tests Skipped :      0
 + Tests Executed :    65
 + Tests Unsupported:   0
 + Tests Passed :      65
 + Tests Failed :       0
 + ------------------------------------------------------- +
Test OK

second and all subsequent invocations:
RTE>>link_bonding_autotest
...
 + ------------------------------------------------------- +
 + Test Suite Summary : Link Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + Tests Total :       65
 + Tests Skipped :      0
 + Tests Executed :    65
 + Tests Unsupported:   0
 + Tests Passed :       5
 + Tests Failed :      60
 + ------------------------------------------------------- +
Test Failed


Looking at the source:
global variable 'test_params' are not reset properly,
plus dynamically allocated resources (mempool, emulated eth-dev, etc.)
are not freed properly.

Comment 2 Ajit Khaparde 2021-10-25 19:24:45 CEST

Konstantin, Is this a regression or has it be this way for a while now? Thanks

Comment 3 Konstantin Ananyev 2021-10-25 22:02:34 CEST

It is definitely not a new one - I see the same issue with 21.08.
I didn't look in details though log history, but my suspicion it always was like that.