From: sys_stv@intel.com
To: test-report@dpdk.org, kumaraparamesh92@gmail.com
Subject: [dpdk-test-report] |FAILURE| pw(106345) sid(21326) job(PER_PATCH_BUILD872)[v2] net/tap: fix to populate fds in secondary process
Date: 24 Jan 2022 22:16:18 -0800 [thread overview]
Message-ID: <4c6944$knfdrm@orsmga005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5447 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/106345
_Compilation issues_
Submitter: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>
Date: 2022-01-24 12:12:51
Reply_mail: 20220124121251.64762-1-kumaraparamesh92@gmail.com
DPDK git baseline: Repo:dpdk-next-net, CommitID: 9cac1db503835c74db16f1b9d6c6c15659acc89c
Meson Build Summary: 20 Builds Done, 18 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 |
| 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: 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/''
[3152/3567] Compiling C object app/dpdk-test-eventdev.p/test-eventdev_test_pipeline_atq.c.o
[3153/3567] Compiling C object app/dpdk-test-flow-perf.p/test-flow-perf_items_gen.c.o
[3154/3567] Linking static target drivers/librte_event_octeontx.a
[3155/3567] Compiling C object app/dpdk-test-eventdev.p/test-eventdev_test_perf_common.c.o
[3156/3567] Compiling C object app/dpdk-test-flow-perf.p/test-flow-perf_actions_gen.c.o
[3157/3567] Compiling C object app/dpdk-test-eventdev.p/test-eventdev_test_perf_atq.c.o
[3158/3567] Compiling C object app/dpdk-test-eventdev.p/test-eventdev_test_order_queue.c.o
[3159/3567] Compiling C object app/dpdk-test-flow-perf.p/test-flow-perf_main.c.o
[3160/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/''
[3084/3553] Generating rte_baseband_null.sym_chk with a meson_exe.py custom command
[3085/3553] Compiling C object drivers/libtmp_rte_event_octeontx.a.p/event_octeontx_ssovf_worker.c.o
[3086/3553] Generating rte_baseband_turbo_sw.pmd.c with a custom command
[3087/3553] Compiling C object app/dpdk-test-acl.p/test-acl_main.c.o
[3088/3553] Compiling C object app/dpdk-test-bbdev.p/test-bbdev_test_bbdev_vector.c.o
[3089/3553] Compiling C object app/dpdk-test-bbdev.p/test-bbdev_test_bbdev.c.o
[3090/3553] Compiling C object app/dpdk-pdump.p/pdump_main.c.o
[3091/3553] Compiling C object drivers/libtmp_rte_event_dsw.a.p/event_dsw_dsw_event.c.o
[3092/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-25 6:16 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='4c6944$knfdrm@orsmga005-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=kumaraparamesh92@gmail.com \
--cc=test-report@dpdk.org \
/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).