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-virtio daily Intel builds
Date: 27 Jan 2022 21:04:46 -0800	[thread overview]
Message-ID: <5975f8$eaap0r@orsmga006-auth.jf.intel.com> (raw)

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


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


commit d6321ffd9c8315ec6b32dc255017e5146b1421b1
Author: Maxime Coquelin <maxime.coquelin@redhat.com>
Date:   Wed Jan 26 10:55:10 2022 +0100

    vhost: use proper logging type for data path

DPDK git Repo: dpdk-next-virtio 


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/''
[3146/3567] Linking target drivers/librte_event_octeontx.so.22.1
[3147/3567] Linking target app/dpdk-proc-info
[3148/3567] Linking target app/dpdk-dumpcap
[3149/3567] Linking target app/dpdk-test-compress-perf
[3150/3567] Linking target app/dpdk-test-acl
[3151/3567] Linking target app/dpdk-pdump
[3152/3567] Linking target app/dpdk-test-cmdline
[3153/3567] Linking target app/dpdk-test-fib
[3154/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/''
[3101/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_verify.c.o
[3102/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_main.c.o
[3103/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_throughput.c.o
[3104/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_options_parse.c.o
[3105/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_cyclecount.c.o
[3106/3553] Compiling C object drivers/libtmp_rte_event_octeontx.a.p/event_octeontx_ssovf_worker.c.o
[3107/3553] Compiling C object drivers/libtmp_rte_event_dsw.a.p/event_dsw_dsw_event.c.o
[3108/3553] Compiling C object app/dpdk-test-compress-perf.p/test-compress-perf_comp_perf_test_common.c.o
[3109/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-28  5:04 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  5:04 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-21 23:52 sys_stv
2023-05-20 23:52 sys_stv
2023-05-20  0:06 sys_stv
2023-05-19  0:19 sys_stv
2023-05-18  1:47 sys_stv
2023-05-17  0:08 sys_stv
2023-05-15 23:53 sys_stv
2023-01-09 23:35 sys_stv
2023-01-09  8:21 sys_stv
2022-11-29  0:04 sys_stv
2022-11-28 11:29 sys_stv
2022-11-23 23:54 sys_stv
2022-11-23  8:12 sys_stv
2022-10-31  4:54 sys_stv
2022-10-13 23:16 sys_stv
2022-09-20 23:29 sys_stv
2022-09-19  7:00 sys_stv
2022-09-19  4:14 sys_stv
2022-09-12 22:44 sys_stv
2022-09-11 23:00 sys_stv
2022-09-09  2:55 sys_stv
2022-09-08 22:53 sys_stv
2022-09-07 14:05 sys_stv
2022-09-07  9:57 sys_stv
2022-09-06 22:43 sys_stv
2022-08-29  7:27 sys_stv
2022-08-25 22:49 sys_stv
2022-06-27  6:06 sys_stv
2022-06-26 22:34 sys_stv
2022-06-25 22:33 sys_stv
2022-06-24 22:33 sys_stv
2022-06-06 22:39 sys_stv
2022-06-01 22:32 sys_stv
2022-06-01  4:53 sys_stv
2022-05-31 22:32 sys_stv
2022-05-31 16:53 sys_stv
2022-05-31 10:53 sys_stv
2022-05-31  4:53 sys_stv
2022-05-30 22:39 sys_stv
2022-05-18 22:35 sys_stv
2022-05-17 22:35 sys_stv
2022-05-17 16:54 sys_stv
2022-05-17 11:06 sys_stv
2022-05-16 22:46 sys_stv
2022-05-07  4:56 sys_stv
2022-05-06 22:46 sys_stv
2022-02-15  8:03 sys_stv
2022-01-28 11:04 sys_stv
2022-01-28  9:42 sys_stv
2022-01-27 23:04 sys_stv
2022-01-27 17:04 sys_stv
2022-01-27 11:05 sys_stv
2022-01-27  8:15 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='5975f8$eaap0r@orsmga006-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).