[V2,4/5] test_plans/pmd_bonded: modify script to adapt changes in dpdk

Message ID 20230217122023.2345221-5-songx.jiale@intel.com (mailing list archive)
State Accepted
Headers
Series modify script to adapt changes in dpdk |

Commit Message

Jiale, SongX Feb. 17, 2023, 12:20 p.m. UTC
  the display information of the binding port in dpdk-testpmd has changed.
modify the script to adapt to this change.

According to dpdk commit f3b5f3d35c59e1("app/testpmd: use dump API to show bonding info").

Signed-off-by: Song Jiale <songx.jiale@intel.com>
---
 test_plans/pmd_bonded_test_plan.rst | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)
  

Patch

diff --git a/test_plans/pmd_bonded_test_plan.rst b/test_plans/pmd_bonded_test_plan.rst
index a76ac6b8..dde885d2 100644
--- a/test_plans/pmd_bonded_test_plan.rst
+++ b/test_plans/pmd_bonded_test_plan.rst
@@ -105,18 +105,20 @@  Create bonded device, add first slave, verify default bonded device has default
     testpmd> add bonding slave 1 4
     Adding port 1 as slave
     testpmd> show bonding config 4
-        Bonding mode: 1
-        Slaves: [1]
-        Active Slaves: []
-        Failed to get primary slave for port=4
+    - Dev basic:
+      Bonding mode: ACTIVE_BACKUP(1)
+      Slaves (1): [1]
+      Active Slaves: []
+      Current Primary: [1]
     testpmd> port start 4
     ......
     Done
     testpmd> show bonding config 4
-        Bonding mode: 1
-        Slaves: [1]
-        Active Slaves: [1]
-        Primary: [1]
+    - Dev basic:
+      Bonding mode: ACTIVE_BACKUP(1)
+      Slaves (1): [1]
+      Active Slaves: [1]
+      Current Primary: [1]
 
 Create another bonded device, and check if the slave added to bonded device1 can't be added to bonded device2::