From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 7807C2B89 for ; Thu, 24 Mar 2016 08:55:38 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP; 24 Mar 2016 00:55:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,384,1455004800"; d="scan'208";a="72334781" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga004.fm.intel.com with ESMTP; 24 Mar 2016 00:55:38 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 24 Mar 2016 00:55:36 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.24]) by shsmsx102.ccr.corp.intel.com ([169.254.2.232]) with mapi id 14.03.0248.002; Thu, 24 Mar 2016 15:55:33 +0800 From: "Liu, Yong" To: Thomas Monjalon , sys_stv , "Cao, Waterman" CC: DPDK_SW_ENG , NPG SW Core Tools PRC , "test-report@dpdk.org" Thread-Topic: [dpdk-test-report] | ERROR | daily Intel builds (29/47) Thread-Index: AQHRhIY+vUoTL1ojS0iw5ApomGjRj59mVWUAgAHlobA= Date: Thu, 24 Mar 2016 07:55:32 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E14ECF5A3@SHSMSX103.ccr.corp.intel.com> References: <0416cf$242sbk@fmsmga004.fm.intel.com> <2097148.SushTU6EDT@xps13> In-Reply-To: <2097148.SushTU6EDT@xps13> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTA5MzY5ZWEtN2RiZi00M2VhLWE1NjQtMGIxZDc2MTUxYzY1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlwvUFpXYjFZQ01UbHFFQzZqWkN1VElpZm5GMytUMFlJaUxrWUNHWGNGVk5JPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 24 Mar 2016 09:02:39 +0100 Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (29/47) X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: automatic test reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2016 07:55:38 -0000 > -----Original Message----- > From: test-report [mailto:test-report-bounces@dpdk.org] On Behalf Of > Thomas Monjalon > Sent: Wednesday, March 23, 2016 6:54 PM > To: sys_stv; Cao, Waterman > Cc: DPDK_SW_ENG; NPG SW Core Tools PRC; test-report@dpdk.org > Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (29/47) >=20 > 2016-03-22 15:00, sys_stv@intel.com: > > Last commit Time : Tue Mar 22 20:46:53 2016 +0100 > > Last Author : Thomas Monjalon >=20 > I am not the author. Please fix it. > The author is retrieved with git log -1 --format=3D'%an' >=20 > > Failure #18 > > OS : FC21_32 / 3.18.8-201 > > Compiler : GCC 4.9.2 > > Build Configuration: i686-native-linuxapp-gcc > > CONFIG_RTE_LIBRTE_PMD_PCAP=3Dy, > > CONFIG_RTE_NIC_BYPASS=3Dy, > > CONFIG_RTE_BUILD_SHARED_LIB=3Dy, > > CONFIG_RTE_LIBRTE_VHOST=3Dy > > > > Makefile:54: *** The RTE_TARGET chosen is not compatible with this > environment (x86_64), for this application. Please change the definition > of the RTE_TARGET environment variable, or run the application on a 32- > bit OS. Stop. > > DPDK/mk/rte.extsubdir.mk:46: recipe for target 'dpdk_qat' failed > > DPDK/mk/rte.sdkexamples.mk:52: recipe for target 'i686-native-linuxapp- > gcc_examples' failed > > DPDK/mk/rte.sdkroot.mk:119: recipe for target 'examples' failed >=20 > Please put a clear separation between failures and success. >=20 > > UBT144_32 / Linux 3.13.0-30 / GCC 4.8.2 >=20 > There are some double spaces here. >=20 Will remove blank lines. > > Config: i686-native-linuxapp-gcc > > CONFIG_RTE_LIBRTE_PMD_PCAP=3Dy, > > CONFIG_RTE_NIC_BYPASS=3Dy, > > CONFIG_RTE_BUILD_SHARED_LIB=3Dy, > > CONFIG_RTE_LIBRTE_VHOST=3Dy >=20 > This presentation is simple and good. > Why it is different in failure cases? Successful build log and failure build log will use same format today. Last time we focus on build error log in last modification and left the for= mat behind. Best regards, Marvin