automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com
Subject: [dpdk-test-report] |FAILURE| pw38395[dpdk-dev] lib/librte_ip_frag:fix ip frag process log
Date: 19 Apr 2018 02:46:54 -0700	[thread overview]
Message-ID: <0590c7$1eqsnv@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4652 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38395

_Compilation issues_

Submitter: li han <han.li1@zte.com.cn>
Date: 2018-04-18 08:37:22
DPDK git baseline: Repo:dpdk-master, CommitID: e62f3a8a04768352bc78389d499be50c923bf6aa

Build Summary: 15 Builds Done, 14 Successful, 1 Failures

Test environment and configuration as below:

OS: FC25
	Kernel Version: 4.9.13-100.fc24.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
	Clang Version: 3.8.0 (tags/RELEASE_380/final)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc-debug

OS: FC24
	Kernel Version: 4.9.13-100.fc24.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
	Clang Version: 3.8.0 (tags/RELEASE_380/final)
	i686-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc-shared
	x86_64-native-linuxapp-clang

OS: CENTOS
	Kernel Version: 3.10.0-514.10.2.el7.x86_64
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc-shared
	x86_64-native-linuxapp-gcc
	i686-native-linuxapp-gcc

OS: UB1604
	Kernel Version: 4.4.0-81-generic
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
	GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
	Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
	x86_64-native-linuxapp-gcc
	i686-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc-shared
	x86_64-native-linuxapp-clang

OS: FreeBSD
	Kernel Version: 10.3-RELEASE
	CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.74-MHz K8-class CPU)
	GCC Version: gcc (FreeBSD Ports Collection) 4.8.5
	Clang Version: 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang

Failed Build #1:
OS: FC25
Target: x86_64-native-linuxapp-gcc-debug
  CC ip_frag_internal.o
  CC virtio_net.o
In file included from /tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/x86_64-native-linuxapp-gcc/include/rte_jhash.h:52:0,
                 from /tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/lib/librte_ip_frag/ip_frag_internal.c:7:
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/lib/librte_ip_frag/ip_frag_internal.c: In function ‘ip_frag_process’:
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/lib/librte_ip_frag/ip_frag_internal.c:157:3: error: expected ‘)’ before ‘i’
   i  "first fragment: ofs: %u, len: %u\n"
   ^
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/x86_64-native-linuxapp-gcc/include/rte_log.h:336:32: note: in definition of macro ‘RTE_LOG’
    RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
                                ^~~~~~~~~~~
--
    RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
                         ^
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/lib/librte_ip_frag/ip_frag_internal.c:154:4: note: in expansion of macro ‘IP_FRAG_LOG’
    IP_FRAG_LOG(DEBUG, "%s:%d invalid fragmented packet:\n"
    ^~~~~~~~~~~
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target 'ip_frag_internal.o' failed
make[5]: *** [ip_frag_internal.o] Error 1
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/mk/rte.subdir.mk:35: recipe for target 'librte_ip_frag' failed
make[4]: *** [librte_ip_frag] Error 2
make[4]: *** Waiting for unfinished jobs....
  CC vdpa.o
  CC vhost_crypto.o
  AR librte_vhost.a
  INSTALL-LIB librte_vhost.a
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/mk/rte.sdkbuild.mk:49: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
make[2]: *** [all] Error 2
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
make[1]: *** [pre_install] Error 2
/tmp/FC25_K4.8.6_GCC6.3.1/x86_64-native-linuxapp-gcc-debug/6e9d3ff8a10a442a89a49193d823b279/dpdk/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
make: *** [install] Error 2

DPDK STV team

                 reply	other threads:[~2018-04-19  9:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='0590c7$1eqsnv@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.org \
    --cc=xinfengx.zhao@intel.com \
    --cc=zhaoyan.chen@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).