From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Tom Jones <thj@freebsd.org>
Subject: |FAILURE| pw138654 [PATCH] net/vmxnet3: Don't enable rx queue interr
Date: Thu, 21 Mar 2024 05:56:27 -0700 (PDT) [thread overview]
Message-ID: <65fc2e7b.050a0220.615a1.c7e8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320130255.1526-1-thj@freebsd.org>
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138654
_Testing issues_
Submitter: Tom Jones <thj@freebsd.org>
Date: Wednesday, March 20 2024 13:02:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31a4216a9ee3c02cf2443d533f6a491cdb25904e
138654 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+-------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| CentOS Stream 8 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 9 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 37 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| openSUSE Leap 15 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 38 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Debian 11 (arm) | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 20.04 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.2 | FAIL | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS | PASS | PASS |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 22.04 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| RHEL8 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Debian Bullseye | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
| Alpine | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+-------------------+
==== 20 line log output for FreeBSD 13.2 (dpdk_meson_compile): ====
[1403/1841] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_rte_cryptodev_scheduler.c.o
[1404/1841] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_failover.c.o
[1405/1841] Generating drivers/rte_crypto_null.pmd.c with a custom command
[1406/1841] Compiling C object drivers/librte_crypto_null.a.p/meson-generated_.._rte_crypto_null.pmd.c.o
[1407/1841] Linking static target drivers/librte_crypto_null.a
[1408/1841] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_multicore.c.o
[1409/1841] Compiling C object drivers/librte_crypto_null.so.24.1.p/meson-generated_.._rte_crypto_null.pmd.c.o
[1410/1841] Compiling C object drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_ethdev.c.o
FAILED: drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_ethdev.c.o
ccache cc -Idrivers/libtmp_rte_net_vmxnet3.a.p -Idrivers -I../drivers -Idrivers/net/vmxnet3 -I../drivers/net/vmxnet3 -Ilib/ethdev -I../lib/ethdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/freebsd/include -I../lib/eal/freebsd/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/bsd -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -I/usr/local/include -fcolor-diagnostics -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prot
otypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -D__BSD_VISIBLE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-unused-parameter -Wno-unused-value -Wno-strict-aliasing -Wno-format-extra-args -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.vmxnet3 -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_ethdev.c.o -MF drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_ethdev.c.o.d -o drivers/libtmp_rte_net_vmxnet3.a.p/net_vmxnet3_vmxnet3_ethdev.c.o -c ../drivers/net/vmxnet3/vmxnet3_ethdev.c
../drivers/net/vmxnet3/vmxnet3_ethdev.c:1939:21: error: unused variable 'hw' [-Werror,-Wunused-variable]
struct vmxnet3_hw *hw = dev->data->dev_private;
^
1 error generated.
[1411/1841] Compiling C object drivers/libtmp_rte_crypto_scheduler.a.p/crypto_scheduler_scheduler_pkt_size_distr.c.o
[1412/1841] Generating drivers/rte_crypto_openssl.pmd.c with a custom command
[1413/1841] Generating drivers/rte_crypto_bcmfs.pmd.c with a custom command
[1414/1841] Linking target drivers/librte_crypto_null.so.24.1
[1415/1841] Generating drivers/rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 14.0.5
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Alpine
Kernel: 5.4.0-167-generic
Compiler: gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29618/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-21 13:00 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320130255.1526-1-thj@freebsd.org>
2024-03-21 7:20 ` |SUCCESS| pw138654 [PATCH] net/vmxnet3: Don't enable rx queue interrupts on FreeBSD qemudev
2024-03-21 7:25 ` qemudev
2024-03-21 7:44 ` checkpatch
2024-03-21 10:57 ` |SUCCESS| pw138654 [PATCH] net/vmxnet3: Don't enable rx queue interr dpdklab
2024-03-21 11:10 ` dpdklab
2024-03-21 11:19 ` dpdklab
2024-03-21 11:20 ` dpdklab
2024-03-21 11:24 ` dpdklab
2024-03-21 11:27 ` dpdklab
2024-03-21 11:28 ` dpdklab
2024-03-21 11:40 ` dpdklab
2024-03-21 11:41 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:43 ` dpdklab
2024-03-21 11:44 ` dpdklab
2024-03-21 11:45 ` dpdklab
2024-03-21 11:50 ` dpdklab
2024-03-21 11:50 ` dpdklab
2024-03-21 11:50 ` dpdklab
2024-03-21 11:51 ` dpdklab
2024-03-21 12:05 ` dpdklab
2024-03-21 12:12 ` dpdklab
2024-03-21 12:12 ` dpdklab
2024-03-21 12:13 ` dpdklab
2024-03-21 12:15 ` dpdklab
2024-03-21 12:34 ` dpdklab
2024-03-21 12:50 ` |FAILURE| " dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:53 ` |SUCCESS| " dpdklab
2024-03-21 12:53 ` |FAILURE| " dpdklab
2024-03-21 12:53 ` dpdklab
2024-03-21 12:53 ` |SUCCESS| " dpdklab
2024-03-21 12:53 ` |FAILURE| " dpdklab
2024-03-21 12:53 ` |SUCCESS| " dpdklab
2024-03-21 12:54 ` |FAILURE| " dpdklab
2024-03-21 12:54 ` |SUCCESS| " dpdklab
2024-03-21 12:54 ` dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:55 ` |FAILURE| " dpdklab
2024-03-21 12:55 ` |SUCCESS| " dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:56 ` dpdklab
2024-03-21 12:56 ` |FAILURE| " dpdklab
2024-03-21 12:56 ` dpdklab [this message]
2024-03-21 12:57 ` |SUCCESS| " dpdklab
2024-03-21 12:57 ` dpdklab
2024-03-21 12:57 ` dpdklab
2024-03-21 12:57 ` dpdklab
2024-03-21 12:59 ` dpdklab
2024-03-21 12:59 ` dpdklab
2024-03-21 12:59 ` dpdklab
2024-03-21 13:00 ` dpdklab
2024-03-21 13:00 ` dpdklab
2024-03-21 13:02 ` dpdklab
2024-03-21 13:03 ` dpdklab
2024-03-21 13:04 ` dpdklab
2024-03-21 13:05 ` dpdklab
2024-03-21 13:06 ` dpdklab
2024-03-21 13:08 ` dpdklab
2024-03-21 13:09 ` dpdklab
2024-03-21 13:10 ` dpdklab
2024-03-21 13:11 ` dpdklab
2024-03-21 13:12 ` dpdklab
2024-03-21 13:26 ` dpdklab
2024-03-21 14:03 ` dpdklab
2024-03-21 16:30 ` dpdklab
2024-03-21 16:43 ` dpdklab
2024-03-22 2:11 ` dpdklab
2024-03-23 9:50 ` dpdklab
2024-03-23 10:27 ` 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=65fc2e7b.050a0220.615a1.c7e8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thj@freebsd.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).