[dpdk-test-report] | ERROR | daily Intel builds (29/47)

Liu, Yong yong.liu at intel.com
Thu Mar 24 08:55:32 CET 2016



> -----Original Message-----
> From: test-report [mailto:test-report-bounces at 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 at dpdk.org
> Subject: Re: [dpdk-test-report] | ERROR | daily Intel builds (29/47)
> 
> 2016-03-22 15:00, sys_stv at 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


More information about the test-report mailing list