automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xiaoyun Li <xiaoyun.li@intel.com>
Subject: |FAILURE| pw104853-104854 [PATCH] [v4, 2/2] testpmd: fix l4 sw csum over multi segments
Date: Fri,  3 Dec 2021 13:21:12 -0500 (EST)	[thread overview]
Message-ID: <20211203182112.C18C63155@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/104854

_Testing issues_

Submitter: Xiaoyun Li <xiaoyun.li@intel.com>
Date: Friday, December 03 2021 11:38:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:042f5a355a57b31a9f87824173a9d427b21abdb8

104853-104854 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | FAIL               | PASS                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 31           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS 8            | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 32           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL 7              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Arch Linux          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 33           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34 clang     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+

==== 20 line log output for Windows Server 2019 (dpdk_meson_compile): ====
[322/617] Generating rte_dma_idxd.pmd.c with a custom command (wrapped by meson to set PATH)
[323/617] Linking target lib/rte_cryptodev-22.dll
Creating library lib\rte_cryptodev.lib and object lib\rte_cryptodev.exp
[324/617] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_manage.c.obj
[325/617] Linking target lib/rte_net-22.dll
FAILED: lib/rte_net-22.dll
"clang"  -Wl,/MACHINE:X64 -Wl,/OUT:lib/rte_net-22.dll lib/net/libnet_crc_avx512_lib.a.p/net_crc_avx512.c.obj lib/librte_net.a.p/net_rte_arp.c.obj lib/librte_net.a.p/net_rte_ether.c.obj lib/librte_net.a.p/net_rte_net.c.obj lib/librte_net.a.p/net_rte_net_crc.c.obj lib/librte_net.a.p/net_net_crc_sse.c.obj "-Wl,/nologo" "-Wl,/release" "-Wl,/nologo" "-Wl,/OPT:REF" "-Wl,/DLL" "-Wl,/IMPLIB:lib\rte_net.lib" "lib\rte_eal.lib" "lib\rte_kvargs.lib" "lib\rte_mbuf.lib" "lib\rte_mempool.lib" "lib\rte_ring.lib" "lib\rte_telemetry.lib" "-Wl,/def:C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Meson\dpdk\build\lib\rte_net_exports.def" "-ldbghelp" "-lsetupapi" "-lws2_32" "-lmincore" "-lkernel32" "-luser32" "-lgdi32" "-lwinspool" "-lshell32" "-lole32" "-loleaut32" "-luuid" "-lcomdlg32" "-ladvapi32"
rte_net_exports.def : error LNK2001: unresolved external symbol rte_ipv4_udptcp_cksum_mbuf
rte_net_exports.def : error LNK2001: unresolved external symbol rte_ipv4_udptcp_cksum_mbuf_verify
rte_net_exports.def : error LNK2001: unresolved external symbol rte_ipv6_udptcp_cksum_mbuf
rte_net_exports.def : error LNK2001: unresolved external symbol rte_ipv6_udptcp_cksum_mbuf_verify
lib\rte_net.lib : fatal error LNK1120: 4 unresolved externals
clang: error: linker command failed with exit code 1120 (use -v to see invocation)
[326/617] Linking target lib/rte_gpudev-22.dll
Creating library lib\rte_gpudev.lib and object lib\rte_gpudev.exp
[327/617] Generating rte_mempool_stack.pmd.c with a custom command (wrapped by meson to set PATH)
[328/617] Compiling C object drivers/librte_dma_idxd.a.p/meson-generated_.._rte_dma_idxd.pmd.c.obj
[329/617] Generating rte_dma_skeleton.pmd.c with a custom command (wrapped by meson to set PATH)
[330/617] Generating symbol file lib/rte_cryptodev-22.dll.p/rte_cryptodev-22.dll.symbols
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 9.0 and gcc 8.1.0 (MinGW)

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

CentOS 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20434/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2021-12-03 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 18:21 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-03 19:00 dpdklab
2021-12-03 18:09 dpdklab
2021-12-03 17:58 dpdklab

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=20211203182112.C18C63155@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=xiaoyun.li@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).