From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V2] tests/iavf_fdir: optimization script
Date: Mon, 8 Nov 2021 13:10:16 +0800 [thread overview]
Message-ID: <1636348216-211815-1-git-send-email-songx.jiale@intel.com> (raw)
initialize pf. because pf is not initialized after case test, other case tests fail
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
tests/TestSuite_iavf_fdir.py | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
mode change 100755 => 100644 tests/TestSuite_iavf_fdir.py
diff --git a/tests/TestSuite_iavf_fdir.py b/tests/TestSuite_iavf_fdir.py
old mode 100755
new mode 100644
index fab7cc27..6abb75c5
--- a/tests/TestSuite_iavf_fdir.py
+++ b/tests/TestSuite_iavf_fdir.py
@@ -7593,6 +7593,7 @@ class TestIAVFFdir(TestCase):
"""
Run before each test case.
"""
+ self.dut.restore_interfaces_linux()
self.setup_2pf_4vf_env()
time.sleep(1)
self.launch_testpmd()
@@ -8344,7 +8345,6 @@ class TestIAVFFdir(TestCase):
create same rules on pf and vf, no conflict
"""
self.dut.kill_all()
- self.setup_2pf_4vf_env()
self.session_secondary = self.dut.new_session()
self.session_third = self.dut.new_session()
@@ -8496,7 +8496,6 @@ class TestIAVFFdir(TestCase):
create same input set but different action rules on pf and vf, no conflict.
"""
self.dut.kill_all()
- self.setup_2pf_4vf_env()
self.session_secondary = self.dut.new_session()
self.session_third = self.dut.new_session()
@@ -9810,7 +9809,6 @@ class TestIAVFFdir(TestCase):
def tear_down(self):
# destroy all flow rule on port 0
- self.dut.kill_all()
self.destroy_env()
if getattr(self, 'session_secondary', None):
self.dut.close_session(self.session_secondary)
--
2.17.1
next reply other threads:[~2021-11-08 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 5:10 Jiale Song [this message]
2021-11-08 15:31 ` Tu, Lijuan
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=1636348216-211815-1-git-send-email-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).