From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw90568 [PATCH] net/ena: fix releasing Tx ring mbufs
Date: Mon, 5 Apr 2021 16:32:03 -0400 (EDT) [thread overview]
Message-ID: <20210405203203.780156053E@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 5694 bytes --]
Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/90568
_Testing issues_
Submitter: David Harton <dharton@cisco.com>
Date: Monday, April 05 2021 18:57:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:aa9cb78f66c53728593c1f65f69f2bbc7ca4a4a9
90568 --> 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 |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Fedora 32 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 | SKIPPED | PASS | FAIL | FAIL |
+---------------------+----------------------+--------------------+-------------------+----------------+
| CentOS Stream 8 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| FreeBSD 11.2 | SKIPPED | FAIL | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| RHEL8 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Fedora 31 | SKIPPED | PASS | FAIL | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 20.04 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| RHEL 7 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| openSUSE Leap 15 | SKIPPED | FAIL | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Arch Linux | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 ARM | SKIPPED | FAIL | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
==== 20 line log output for Fedora 31 (dpdk_compile_spdk): ====
915 | struct rte_mbuf **mbufs, unsigned count)
| ~~~~~~~~~~~~~~~~~~^~~~~
../drivers/net/ena/ena_ethdev.c:1491:40: error: passing argument 2 of ‘rte_pktmbuf_alloc_bulk’ from incompatible pointer type [-Werror=incompatible-pointer-types]
1491 | rte_pktmbuf_alloc_bulk(rxq->mb_pool, (void **)(&mbufs[i]),
| ^~~~~~~~~~~~~~~~~~~~
| |
| void **
In file included from ../lib/librte_net/rte_ether.h:23,
from ../drivers/net/ena/ena_ethdev.c:7:
../lib/librte_mbuf/rte_mbuf.h:915:21: note: expected ‘struct rte_mbuf **’ but argument is of type ‘void **’
915 | struct rte_mbuf **mbufs, unsigned count)
| ~~~~~~~~~~~~~~~~~~^~~~~
cc1: all warnings being treated as errors
[1228/2881] Generating rte_net_enetc.pmd.c with a custom command
[1229/2881] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_base_vnic_wq.c.o
[1230/2881] Generating rte_net_e1000.sym_chk with a custom command (wrapped by meson to capture output)
[1231/2881] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_ethdev.c.o
[1232/2881] Compiling C object drivers/libtmp_rte_net_enic.a.p/net_enic_enic_flow.c.o
ninja: build stopped: subcommand failed.
[1] Error running command.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0 and gcc 8.1.0 (MinGW)
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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)
openSUSE Leap 15
Kernel: 4.12.14
Compiler: gcc 7.4.1
Arch Linux
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.0
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/16298/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-04-05 20:32 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=20210405203203.780156053E@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).