automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, thomas@monjalon.net
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com
Subject: [dpdk-test-report] |FAILURE| dpdk-next-eventdev daily Intel builds
Date: 09 Jan 2023 13:48:30 -0800	[thread overview]
Message-ID: <5f0cd1$mp1e07@fmsmga002-auth.fm.intel.com> (raw)

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


Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_


commit 373f4c7de8ff350548cacc3d56e788461677f2c7
Author: David Marchand <david.marchand@redhat.com>
Date:   Tue Dec 13 16:07:10 2022 +0100

    ci: drop Travis configuration

DPDK git Repo: dpdk-next-eventdev 


Meson Build Summary: 27 Builds Done, 26 Successful, 1 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FreeBSD13-64 | pass       | pass         |            | pass       | pass      |          |            |
| RHEL86-64    | pass       | pass         |            | pass       | pass      |          |            |
| SUSE15-64    | pass       | pass         |            |            |           |          |            |
| RHEL90-64    | fail       |              |            |            |           |          |            |
| UB2004-64    | pass       | pass         |            |            |           | pass     |            |
| UB2204-32    | pass       |              |            |            |           |          |            |
| UB2204-64N   | pass       |              |            | pass       |           |          |            |
| UB2204-64    | pass       | pass         |            |            |           | pass     | pass       |
| CentOS79-64  | pass       |              |            |            |           |          |            |
| RHEL86-64Rt  | pass       |              |            |            |           |          |            |
| UB2210-64    | pass       |              |            |            |           |          |            |
| FC37-64      | pass       | pass         |            |            |           |          |            |
| UB2204-64Rt  | pass       |              |            |            |           |          |            |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+

Comments: 
Because of DPDK bug (https://bugs.dpdk.org/show_bug.cgi?id=928),
All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier. 
 
Test environment and configuration as below:


OS: FreeBSD13-64
	Kernel Version: 13.1-RELEASE
	GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
	Clang Version: 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303)
	x86_64-native-bsdapp-gcc
	x86_64-native-bsdapp-clang
	x86_64-native-bsdapp-gcc+shared
	x86_64-native-bsdapp-gcc+debug

OS: RHEL86-64
	Kernel Version: 4.18.0-372.9.1.el8.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
	Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug

OS: SUSE15-64
	Kernel Version: 5.14.21-150400.22-default
	GCC Version: gcc (SUSE Linux) 7.5.0
	Clang Version: 11.0.1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc

OS: RHEL90-64
	Kernel Version: 5.14.0-162.6.1.el9_1.x86_64
	GCC Version: gcc (GCC) 11.3.1 20220421 (Red Hat 11.3.1-2)
	Clang Version: 14.0.6 (Red Hat 14.0.6-1.el9)
	x86_64-native-linuxapp-gcc

OS: UB2004-64
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-doc

OS: UB2204-32
	Kernel Version: 5.15.0-25-generic
	GCC Version: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
	Clang Version: NA
	i686-native-linuxapp-gcc

OS: UB2204-64N
	Kernel Version: 5.17.5-051705-generic
	GCC Version: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
	Clang Version: 14.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc+shared

OS: UB2204-64
	Kernel Version: 5.15.0-25-generic
	GCC Version: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
	Clang Version: 14.0.0-1ubuntu1
	x86_64-native-linuxapp-gcc+16byte
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-doc

OS: CentOS79-64
	Kernel Version: 3.10.0-1160.81.1.el7.x86_64
	GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
	Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
	x86_64-native-linuxapp-gcc

OS: RHEL86-64Rt
	Kernel Version: 4.18.0-372.9.1.rt7.166.el8.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
	Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
	x86_64-native-linuxapp-gcc

OS: UB2210-64
	Kernel Version: 5.19.0-21-generic
	GCC Version: gcc (Ubuntu 12.2.0-3ubuntu1) 12.2.0
	Clang Version: 15.0.2-1
	x86_64-native-linuxapp-gcc

OS: FC37-64
	Kernel Version: 6.0.15-300.fc37.x86_64
	GCC Version: gcc (GCC) 12.2.1 20221121 (Red Hat 12.2.1-4)
	Clang Version: 15.0.6 (Fedora 15.0.6-2.fc37)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

OS: UB2204-64Rt
	Kernel Version: 5.8.0-48-generic
	GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-gcc



*Build Failed #1:
OS: RHEL90-64
Target: x86_64-native-linuxapp-gcc
FAILED: kernel/linux/kni/rte_kni.ko 
/usr/bin/make -j4 -C /lib/modules/5.14.0-162.6.1.el9_1.x86_64/build M=/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni src=/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/kernel/linux/kni 'MODULE_CFLAGS= -DHAVE_ARG_TX_QUEUE -include /root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/config/rte_config.h -I/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/lib/eal/include -I/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/lib/kni -I/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/x86_64-native-linuxapp-gcc -I/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/kernel/linux/kni' modules
make: Entering directory '/usr/src/kernels/5.14.0-162.6.1.el9_1.x86_64'
  CC [M]  /root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni/kni_misc.o
  CC [M]  /root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni/kni_net.o
/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/kernel/linux/kni/kni_net.c: In function ‘kni_net_rx_normal’:
/root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/kernel/linux/kni/kni_net.c:445:17: error: implicit declaration of function ‘netif_rx_ni’; did you mean ‘netif_rx’? [-Werror=implicit-function-declaration]
  445 |                 netif_rx_ni(skb);
      |                 ^~~~~~~~~~~
      |                 netif_rx
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:295: /root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni/kni_net.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1915: /root/RHEL90-64_K5.14.0_GCC11.3.1/x86_64-native-linuxapp-gcc/20230110050837/dpdk/x86_64-native-linuxapp-gcc/kernel/linux/kni] Error 2
make: Leaving directory '/usr/src/kernels/5.14.0-162.6.1.el9_1.x86_64'
[3159/3159] Linking target examples/dpdk-vmdq_dcb
ninja: build stopped


DPDK STV team

             reply	other threads:[~2023-01-09 21:48 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 21:48 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-26 11:28 sys_stv
2023-05-15 22:06 sys_stv
2023-02-08  7:30 sys_stv
2022-11-23 21:51 sys_stv
2022-11-23  6:17 sys_stv
2022-11-22  8:51 sys_stv
2022-10-13 21:40 sys_stv
2022-10-11 21:53 sys_stv
2022-10-07  3:47 sys_stv
2022-09-20  6:29 sys_stv
2022-09-19  3:02 sys_stv
2022-09-15  7:15 sys_stv
2022-09-14 13:13 sys_stv
2022-09-14  3:58 sys_stv
2022-09-13 16:43 sys_stv
2022-09-09 21:30 sys_stv
2022-09-01 21:31 sys_stv
2022-06-26 21:28 sys_stv
2022-06-25 21:28 sys_stv
2022-06-24 21:28 sys_stv
2022-06-06 21:28 sys_stv
2022-06-06 16:57 sys_stv
2022-06-01 23:15 sys_stv
2022-06-01 21:28 sys_stv
2022-06-01  2:18 sys_stv
2022-05-31 23:21 sys_stv
2022-05-31 21:27 sys_stv
2022-05-31 17:25 sys_stv
2022-05-31 11:26 sys_stv
2022-05-31  5:26 sys_stv
2022-05-30 21:28 sys_stv
2022-05-18 23:28 sys_stv
2022-05-18 21:29 sys_stv
2022-05-17 23:30 sys_stv
2022-05-17 21:29 sys_stv
2022-05-17 17:39 sys_stv
2022-05-17 11:39 sys_stv
2022-05-17  9:58 sys_stv
2022-05-16 23:43 sys_stv
2022-05-16 21:38 sys_stv
2022-05-07  5:46 sys_stv
2022-05-06 23:48 sys_stv
2022-05-06 21:31 sys_stv
2022-03-29 21:50 sys_stv
2022-03-12 21:40 sys_stv

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='5f0cd1$mp1e07@fmsmga002-auth.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dpdk_sw_eng@intel.com \
    --cc=npg.sw.core.tools.prc@intel.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).