From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Phanendra Vukkisala <pvukkisala@marvell.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: Vijaya Bhaskar Annayyolla <avijay@marvell.com>,
Faisal Masood <fmasood@marvell.com>
Subject: Re: [dts] [PATCH] tests/TestSuite_efd.py: Increased wait time to run test_efd_unit
Date: Fri, 11 Jan 2019 01:57:57 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9FFDEC@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1546867103-6190-1-git-send-email-pvukkisala@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Phanendra Vukkisala
> Sent: Monday, January 7, 2019 9:19 PM
> To: dts@dpdk.org
> Cc: Vijaya Bhaskar Annayyolla <avijay@marvell.com>; Faisal Masood
> <fmasood@marvell.com>; Phanendra Vukkisala <pvukkisala@marvell.com>
> Subject: [dts] [PATCH] tests/TestSuite_efd.py: Increased wait time to run
> test_efd_unit
>
> From: pvukkisala <pvukkisala@marvell.com>
>
> efd_autotest is not finishing within 60 seconds on cavium device.
> So increased timeout to 120 seconds. Verified test on cavium device.
>
> Signed-off-by: phanendra,vukkisala <pvukkisala@marvell.com>
> ---
> tests/TestSuite_efd.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_efd.py b/tests/TestSuite_efd.py index
> 991f99a..2c80464 100644
> --- a/tests/TestSuite_efd.py
> +++ b/tests/TestSuite_efd.py
> @@ -68,7 +68,7 @@ class TestEFD(TestCase, IxiaPacketGenerator):
> Run EFD unit test
> """
> self.dut.send_expect("./test/test/test -n 1 -c f", "RTE>>", 60)
> - out = self.dut.send_expect("efd_autotest", "RTE>>", 60)
> + out = self.dut.send_expect("efd_autotest", "RTE>>", 120)
> self.dut.send_expect("quit", "# ")
> self.verify("Test OK" in out, "Test failed")
>
> --
> 1.7.9.5
prev parent reply other threads:[~2019-01-11 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 13:18 Phanendra Vukkisala
2019-01-11 1:40 ` Tu, Lijuan
2019-01-11 1:57 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0B9FFDEC@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=pvukkisala@marvell.com \
/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).