From: Ondrej Lichtner <olichtne(a)redhat.com>
Starting with DPDK 18.11 the startup time increased due to different
memory management, this means we need to add artifical wait times for
the startup to not have our results impacted.
This is a workaround and instead an improvement on the dpdk side should
hopefully happen, but until then we'll need this.
Signed-off-by: Ondrej Lichtner <olichtne(a)redhat.com>
---
recipes/regression_tests/phase3/ovs-dpdk-pvp.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/recipes/regression_tests/phase3/ovs-dpdk-pvp.py
b/recipes/regression_tests/phase3/ovs-dpdk-pvp.py
index f905128..512f6f5 100644
--- a/recipes/regression_tests/phase3/ovs-dpdk-pvp.py
+++ b/recipes/regression_tests/phase3/ovs-dpdk-pvp.py
@@ -399,8 +399,11 @@ run_ssh_command_on_guest("mkfifo /tmp/testpmd_stdio",
guest, h2, guest_virtname)
run_ssh_command_on_bg_channel("tail -f /tmp/testpmd_stdio |
{}".format(testpmd_cmd),
testpmd_shell, h2, guest_virtname)
+ctl.wait(20)
run_ssh_command_on_guest("echo \"start tx_first\" >
/tmp/testpmd_stdio", guest, h2, guest_virtname)
+ctl.wait(20)
+
trex_client_mod = ctl.get_module("TRexClient",
options=trex_client_conf)
--
2.20.1