From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V1] tests/vf_pmd_stacked_bonded: optimize script
Date: Mon, 10 Apr 2023 16:22:27 +0000 [thread overview]
Message-ID: <20230410162227.833948-1-songx.jiale@intel.com> (raw)
some nic do not have "link-down-on-close" flags, but they also support
synchronizing the status of the vf port and the port of the peer port.
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
tests/TestSuite_vf_pmd_stacked_bonded.py | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_vf_pmd_stacked_bonded.py b/tests/TestSuite_vf_pmd_stacked_bonded.py
index 5765481e..615e9517 100644
--- a/tests/TestSuite_vf_pmd_stacked_bonded.py
+++ b/tests/TestSuite_vf_pmd_stacked_bonded.py
@@ -566,7 +566,10 @@ class TestVFPmdStackedBonded(TestCase):
"""
Test Case: active-backup stacked bonded rx traffic with slave down
"""
- self.verify(self.default_stats, "tester port not support '%s'" % self.flag)
+ if not self.default_stats:
+ self.logger.warning(
+ "Please ensure that the link status of the vf port can be synchronized with the peer port!!!"
+ )
self.backup_check_traffic_with_slave_down()
def test_mode_xor_rx(self):
@@ -579,7 +582,10 @@ class TestVFPmdStackedBonded(TestCase):
"""
Test Case: balance-xor stacked bonded rx traffic with slave down
"""
- self.verify(self.default_stats, "tester port not support '%s'" % self.flag)
+ if not self.default_stats:
+ self.logger.warning(
+ "Please ensure that the link status of the vf port can be synchronized with the peer port!!!"
+ )
self.xor_check_stacked_rx_one_slave_down()
def tear_down(self):
--
2.25.1
next reply other threads:[~2023-04-10 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 16:22 Jiale Song [this message]
2023-04-11 7:55 ` lijuan.tu
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=20230410162227.833948-1-songx.jiale@intel.com \
--to=songx.jiale@intel.com \
--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).