From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <yong.liu@intel.com>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by dpdk.org (Postfix) with ESMTP id 479FE3979
 for <dts@dpdk.org>; Wed, 18 Nov 2015 02:47:35 +0100 (CET)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
 by orsmga102.jf.intel.com with ESMTP; 17 Nov 2015 17:47:34 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.20,310,1444719600"; d="scan'208";a="853436336"
Received: from stv-crb-56.sh.intel.com (HELO [10.239.128.116])
 ([10.239.128.116])
 by fmsmga002.fm.intel.com with ESMTP; 17 Nov 2015 17:47:33 -0800
Message-ID: <564BD8F7.5010300@intel.com>
Date: Wed, 18 Nov 2015 09:48:39 +0800
From: "Liu, Yong" <yong.liu@intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Dong, ShijieX" <shijiex.dong@intel.com>, 
 "dts@dpdk.org" <dts@dpdk.org>
References: <1447733610-18238-1-git-send-email-shijiex.dong@intel.com>
 <564BD2EC.2040303@intel.com>
 <1F89F50008D18D4EBA598B7DF3E7408901AFF3B8@SHSMSX103.ccr.corp.intel.com>
In-Reply-To: <1F89F50008D18D4EBA598B7DF3E7408901AFF3B8@SHSMSX103.ccr.corp.intel.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dts] [PATCH V1] TIMEOUT on eal_flags_autotest
X-BeenThere: dts@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: test suite reviews and discussions <dts.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dts>,
 <mailto:dts-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dts/>
List-Post: <mailto:dts@dpdk.org>
List-Help: <mailto:dts-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dts>,
 <mailto:dts-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 01:47:35 -0000

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):
>>            """