From: "Liu, Yong" <yong.liu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
sys_stv <sys_stv@intel.com>,
"Cao, Waterman" <waterman.cao@intel.com>
Cc: DPDK_SW_ENG <dpdk_sw_eng@intel.com>,
NPG SW Core Tools PRC <npg.sw.core.tools.prc@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>
Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (29/47)
Date: Thu, 24 Mar 2016 07:55:32 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E14ECF5A3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <2097148.SushTU6EDT@xps13>
> -----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)
>
> 2016-03-22 15:00, sys_stv@intel.com:
> > Last commit Time : Tue Mar 22 20:46:53 2016 +0100
> > Last Author : Thomas Monjalon
>
> I am not the author. Please fix it.
> The author is retrieved with git log -1 --format='%an'
>
> > 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=y,
> > CONFIG_RTE_NIC_BYPASS=y,
> > CONFIG_RTE_BUILD_SHARED_LIB=y,
> > CONFIG_RTE_LIBRTE_VHOST=y
> >
> > 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
>
> Please put a clear separation between failures and success.
>
> > UBT144_32 / Linux 3.13.0-30 / GCC 4.8.2
>
> There are some double spaces here.
>
Will remove blank lines.
> > Config: i686-native-linuxapp-gcc
> > CONFIG_RTE_LIBRTE_PMD_PCAP=y,
> > CONFIG_RTE_NIC_BYPASS=y,
> > CONFIG_RTE_BUILD_SHARED_LIB=y,
> > CONFIG_RTE_LIBRTE_VHOST=y
>
> 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 format behind.
Best regards,
Marvin
prev parent reply other threads:[~2016-03-24 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 22:00 sys_stv
2016-03-23 10:53 ` Thomas Monjalon
2016-03-24 7:55 ` 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=86228AFD5BCD8E4EBFD2B90117B5E81E14ECF5A3@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dpdk_sw_eng@intel.com \
--cc=npg.sw.core.tools.prc@intel.com \
--cc=sys_stv@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=waterman.cao@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).