From: "Liu, Yong" <yong.liu@intel.com>
To: "Dong, ShijieX" <shijiex.dong@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] TIMEOUT on eal_flags_autotest
Date: Wed, 18 Nov 2015 07:22:36 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10F697CC@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1F89F50008D18D4EBA598B7DF3E7408901AFF3D8@SHSMSX103.ccr.corp.intel.com>
It's better to send out new patch:)
> -----Original Message-----
> From: Dong, ShijieX
> Sent: Wednesday, November 18, 2015 9:51 AM
> To: Liu, Yong; dts@dpdk.org
> Subject: RE: [dts] [PATCH V1] TIMEOUT on eal_flags_autotest
>
> I am this is DTS, this value I made two changes, the next time I pay
> attention, this need to re do a patch?
>
> -----Original Message-----
> From: Liu, Yong
> Sent: Wednesday, November 18, 2015 9:49 AM
> To: Dong, ShijieX; dts@dpdk.org
> Subject: Re: [dts] [PATCH V1] TIMEOUT on eal_flags_autotest
>
> But from the log, the timeout value extended from 240 to 300, so i asked
> the question.
> One remind, please create your patch based on latest DTS code, not your
> local code.
>
> On 11/18/2015 09:42 AM, Dong, ShijieX wrote:
> > Hi Liuyong
> > The original value is 60 seconds, I test is 120 seconds. OK, because of
> the "fialed several OS, in order to prevent the other systems but.
> >
> > -----Original Message-----
> > From: Liu, Yong
> > Sent: Wednesday, November 18, 2015 9:23 AM
> > To: Dong, ShijieX; dts@dpdk.org
> > Subject: Re: [dts] [PATCH V1] TIMEOUT on eal_flags_autotest
> >
> > Hi Shijie,
> > As i known that timeout value has been extended. Could you give more
> information why four minutes is still not enough for this test?
> >
> > On 11/17/2015 12:13 PM, Shijie Dong wrote:
> >> add time for exec eal_flags_autotest
> >> Signed-off-by: Shijie Dong <shijiex.dong@intel.com>
> >> ---
> >> tests/TestSuite_unit_tests_eal.py | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/tests/TestSuite_unit_tests_eal.py
> >> b/tests/TestSuite_unit_tests_eal.py
> >> index d0b9696..d6d21e4 100644
> >> --- a/tests/TestSuite_unit_tests_eal.py
> >> +++ b/tests/TestSuite_unit_tests_eal.py
> >> @@ -34,7 +34,7 @@ class TestUnitTestsEal(TestCase):
> >> self.verify('make: Leaving directory' in out, "Compilation
> failed")
> >> [arch, machine, self.env, toolchain] = self.target.split('-')
> >> self.start_test_time = 60
> >> - self.run_cmd_time = 240
> >> + self.run_cmd_time = 300
> >>
> >> def set_up(self):
> >> """
prev parent reply other threads:[~2015-11-18 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 4:13 Shijie Dong
2015-11-18 1:22 ` Liu, Yong
2015-11-18 1:42 ` Dong, ShijieX
2015-11-18 1:48 ` Liu, Yong
2015-11-18 1:50 ` Dong, ShijieX
2015-11-18 7:22 ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E10F697CC@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=shijiex.dong@intel.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).