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-net daily Intel builds
Date: 27 Jan 2022 08:53:43 -0800	[thread overview]
Message-ID: <746b4b$fut7ff@orsmga008-auth.jf.intel.com> (raw)

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


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


commit ca7e327aa2b2adc211564cdd7774815dffceaf8f
Author: Selwin Sebastian <selwin.sebastian@amd.com>
Date:   Tue Jan 25 17:47:47 2022 +0530

    net/axgbe: alter port speed bit range

DPDK git Repo: dpdk-next-net 


Meson Build Summary: 22 Builds Done, 20 Successful, 2 Failures, 0 Blocked

+--------------+------------+--------------+------------+------------+-----------+----------+
| os           | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+--------------+------------+--------------+------------+------------+-----------+----------+
| FC35-64      | pass       | pass         |            |            |           |          |
| FreeBSD13-64 | pass       | pass         |            | pass       | pass      |          |
| RHEL84-64    | pass       | pass         | fail       | pass       | pass      |          |
| SUSE15-64    | pass       | pass         |            |            |           |          |
| UB2004-32    | pass       |              |            |            |           |          |
| UB2004-64    | pass       | pass         | fail       |            |           | pass     |
| UB2004-64N   | pass       |              |            | pass       |           |          |
| UB2110-64    | pass       |              |            |            |           |          |
| RHEL85-64    | pass       |              |            |            |           |          |
+--------------+------------+--------------+------------+------------+-----------+----------+
Test environment and configuration as below:


OS: FC35-64
	Kernel Version: 5.14.16-301.fc35.x86_64
	GCC Version: gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1)
	Clang Version: 13.0.0 (Fedora 13.0.0~rc1-1.fc35)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang

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

OS: RHEL84-64
	Kernel Version: 4.18.0-348.7.1.el8_5.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
	Clang Version: 12.0.1 (Red Hat 12.0.1-4.module_el8.5.0+1025+93159d6c)
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-clang
	x86_64-native-linuxapp-gcc+shared
	x86_64-native-linuxapp-gcc+debug
	x86_64-native-linuxapp-icc

OS: SUSE15-64
	Kernel Version: 5.3.18-57-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: UB2004-32
	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
	i686-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-icc
	x86_64-native-linuxapp-doc

OS: UB2004-64N
	Kernel Version: 5.11.16-051116-generic
	GCC Version: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
	Clang Version: 10.0.0-4ubuntu1
	x86_64-native-linuxapp-gcc
	x86_64-native-linuxapp-gcc+shared

OS: UB2110-64
	Kernel Version: 5.13.0-19-generic
	GCC Version: gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0
	Clang Version: 13.0.0-2
	x86_64-native-linuxapp-gcc

OS: RHEL85-64
	Kernel Version: 4.18.0-348.7.1.el8_5.x86_64
	GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-4)
	Clang Version: 12.0.1 (Red Hat 12.0.1-4.module_el8.5.0+1025+93159d6c)
	x86_64-native-linuxapp-gcc



*Build Failed #1:
OS: RHEL84-64
Target: x86_64-native-linuxapp-icc
FAILED: drivers/librte_event_cnxk.so.22.1 
icc @drivers/librte_event_cnxk.so.22.1.rsp
icc: error #10236: File not found:  ''-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/''
[3134/3567] Compiling C object app/dpdk-test-crypto-perf.p/test-crypto-perf_cperf_test_latency.c.o
[3135/3567] Compiling C object app/dpdk-test-crypto-perf.p/test-crypto-perf_cperf_test_pmd_cyclecount.c.o
[3136/3567] Compiling C object app/dpdk-test-fib.p/test-fib_main.c.o
[3137/3567] Generating rte_event_dsw.sym_chk with a custom command (wrapped by meson to capture output)
[3138/3567] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_common.c.o
[3139/3567] Generating rte_event_octeontx.sym_chk with a custom command (wrapped by meson to capture output)
[3140/3567] Linking target app/dpdk-dumpcap
[3141/3567] Linking target app/dpdk-proc-info
[3142/3567] Compiling C object app/dpdk-test-bbdev.p/test-bbdev_test_bbdev_perf.c.o
ninja: build stopped




*Build Failed #2:
OS: UB2004-64
Target: x86_64-native-linuxapp-icc
FAILED: drivers/librte_event_cnxk.so.22.1 
icc @drivers/librte_event_cnxk.so.22.1.rsp
icc: error #10236: File not found:  ''-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/''
[3095/3553] Generating rte_baseband_turbo_sw.sym_chk with a meson_exe.py custom command
[3096/3553] Compiling C object app/dpdk-test-crypto-perf.p/test-crypto-perf_cperf_test_common.c.o
[3097/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_verify.c.o
[3098/3553] Compiling C object app/dpdk-pdump.p/pdump_main.c.o
[3099/3553] Compiling C object drivers/libtmp_rte_event_octeontx.a.p/event_octeontx_ssovf_worker.c.o
[3100/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_cyclecount.c.o
[3101/3553] Compiling C object drivers/libtmp_rte_event_dsw.a.p/event_dsw_dsw_event.c.o
[3102/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_common.c.o
[3103/3553] Compiling C object app/dpdk-test-bbdev.p/test-bbdev_test_bbdev_perf.c.o
ninja: build stopped


DPDK STV team

             reply	other threads:[~2022-01-27 16:54 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 16:53 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09 15:56 sys_stv
2023-06-09 15:01 sys_stv
2023-06-09 14:43 sys_stv
2023-05-16 22:28 sys_stv
2023-05-15 22:24 sys_stv
2023-04-27  6:48 sys_stv
2023-03-02 16:56 sys_stv
2023-03-02 15:47 sys_stv
2023-01-09 22:06 sys_stv
2022-12-06 14:28 sys_stv
2022-11-18 15:47 sys_stv
2022-10-27  9:09 sys_stv
2022-10-27  2:43 sys_stv
2022-10-27  1:15 sys_stv
2022-10-26  6:07 sys_stv
2022-10-25 22:04 sys_stv
2022-10-20  7:19 sys_stv
2022-10-13 21:56 sys_stv
2022-10-07 10:49 sys_stv
2022-09-21 15:19 sys_stv
2022-09-21  9:30 sys_stv
2022-09-20  6:40 sys_stv
2022-09-19  1:58 sys_stv
2022-09-18 21:40 sys_stv
2022-09-14  4:11 sys_stv
2022-09-13 21:43 sys_stv
2022-09-10 21:43 sys_stv
2022-09-08 10:59 sys_stv
2022-09-07 21:43 sys_stv
2022-09-07  8:56 sys_stv
2022-09-06 21:42 sys_stv
2022-08-08 21:42 sys_stv
2022-06-06  2:27 sys_stv
2022-06-01 21:38 sys_stv
2022-05-31 21:38 sys_stv
2022-05-18 21:40 sys_stv
2022-05-17 21:40 sys_stv
2022-05-17 10:10 sys_stv
2022-05-16 21:50 sys_stv
2022-05-06 21:43 sys_stv
2022-01-28 10:53 sys_stv
2022-01-28  9:30 sys_stv
2022-01-28  4:53 sys_stv
2022-01-27 22:53 sys_stv
2022-01-27 10:53 sys_stv
2022-01-27  5:42 sys_stv
2022-01-27  4:42 sys_stv
2022-01-27  3:32 sys_stv
2022-01-26 22:42 sys_stv
2022-01-26 16:42 sys_stv
2022-01-26  4:43 sys_stv
2022-01-26  3:54 sys_stv
2022-01-25 16:42 sys_stv
2022-01-25  7:32 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='746b4b$fut7ff@orsmga008-auth.jf.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).