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
Subject: [dpdk-test-report] |WARNING| [GIT MASTER] 5c4dd877bb239bbe437785fe5f5267a9739a26a5
Date: Fri,  5 Feb 2021 18:45:06 -0500 (EST)	[thread overview]
Message-ID: <20210205234506.367F0325@noxus.dpdklab.iol.unh.edu> (raw)

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

_Testing issues_

Branch: dpdk-next-net-mlx

5c4dd877bb239bbe437785fe5f5267a9739a26a5 --> testing fail

Test environment and result as below:

+---------------------+----------------------+--------------------+-------------------+----------------+
|     Environment     | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_compile_spdk | dpdk_unit_test |
+=====================+======================+====================+===================+================+
| Windows Server 2019 | PASS                 | PASS               | SKIPPED           | SKIPPED        |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04        | SKIPPED              | PASS               | FAIL              | PASS           |
+---------------------+----------------------+--------------------+-------------------+----------------+
| FreeBSD 11.2        | SKIPPED              | PASS               | SKIPPED           | SKIPPED        |
+---------------------+----------------------+--------------------+-------------------+----------------+
| CentOS 8            | SKIPPED              | PASS               | SKIPPED           | SKIPPED        |
+---------------------+----------------------+--------------------+-------------------+----------------+
| openSUSE Leap 15    | SKIPPED              | PASS               | SKIPPED           | SKIPPED        |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 ARM    | SKIPPED              | PASS               | SKIPPED           | PASS           |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Arch Linux          | SKIPPED              | PASS               | SKIPPED           | SKIPPED        |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Fedora 31           | SKIPPED              | PASS               | FAIL              | SKIPPED        |
+---------------------+----------------------+--------------------+-------------------+----------------+

==== 20 line log output for Fedora 31 (dpdk_compile_spdk): ====
rte_power_pmd_mgmt.c:(.text+0xba): undefined reference to `rte_eth_get_monitor_addr'
/usr/bin/ld.bfd: /dpdk/build/lib/librte_power.a(librte_power_rte_power_pmd_mgmt.c.o): in function `rte_power_ethdev_pmgmt_queue_enable':
rte_power_pmd_mgmt.c:(.text.experimental+0x24): undefined reference to `rte_eth_dev_is_valid_port'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x4f): undefined reference to `rte_eth_dev_info_get'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x117): undefined reference to `rte_eth_add_rx_callback'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x141): undefined reference to `rte_eth_get_monitor_addr'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x18f): undefined reference to `rte_eth_add_rx_callback'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x21e): undefined reference to `rte_eth_add_rx_callback'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x36b): undefined reference to `rte_eth_dev_logtype'
/usr/bin/ld.bfd: /dpdk/build/lib/librte_power.a(librte_power_rte_power_pmd_mgmt.c.o): in function `rte_power_ethdev_pmgmt_queue_disable':
rte_power_pmd_mgmt.c:(.text.experimental+0x3bf): undefined reference to `rte_eth_dev_is_valid_port'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x49f): undefined reference to `rte_eth_remove_rx_callback'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x4d1): undefined reference to `rte_eth_remove_rx_callback'
/usr/bin/ld.bfd: rte_power_pmd_mgmt.c:(.text.experimental+0x4f9): undefined reference to `rte_eth_dev_logtype'
collect2: error: ld returned 1 exit status
make[3]: *** [/spdk/mk/spdk.app.mk:65: /spdk/build/examples/blobcli] Error 1
make[2]: *** [/spdk/mk/spdk.subdirs.mk:44: cli] Error 2
make[1]: *** [/spdk/mk/spdk.subdirs.mk:44: blob] Error 2
make: *** [/spdk/mk/spdk.subdirs.mk:44: examples] Error 2
[2] Error running command.
==== End log output ====

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

Ubuntu 18.04
	Kernel: 4.15.0-generic
	Compiler: gcc 7.5

FreeBSD 11.2
	Kernel: 11.2
	Compiler: gcc 8.3

CentOS 8
	Kernel: 4.18.0.el8_0
	Compiler: gcc 8.3.1

openSUSE Leap 15
	Kernel: 4.12.14
	Compiler: gcc 7.4.1

Ubuntu 18.04 ARM
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Arch Linux
	Kernel: latest
	Compiler: gcc latest

Fedora 31
	Kernel: 5.3.16
	Compiler: gcc 9.2.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/13726/

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2021-02-05 23:45 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=20210205234506.367F0325@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).