From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Renyong Wan <wanry@3snic.com>
Subject: |FAILURE| pw130789-130812 [PATCH] [32/32] net/sssnic: add VF dev sup
Date: Tue, 29 Aug 2023 04:57:29 -0700 (PDT) [thread overview]
Message-ID: <64eddd29.920a0220.ee68d.5d81SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/130812
_Testing issues_
Submitter: Renyong Wan <wanry@3snic.com>
Date: Tuesday, August 29 2023 07:58:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ac1d4db91e9955148e82f2caaa107434409cf35e
130789-130812 --> testing fail
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Ubuntu 20.04 | PASS |
+-----------------+----------------+
| Fedora 37 | FAIL |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
| Fedora 38 | FAIL |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
==== 20 line log output for Fedora 38 (dpdk_unit_test): ====
[1901/2733] Compiling C object 'drivers/a715181@@rte_net_softnic@sta/meson-generated_.._rte_net_softnic.pmd.c.o'.
[1902/2733] Linking static target drivers/librte_net_softnic.a.
[1903/2733] Compiling C object 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_workq.c.o'.
[1904/2733] Compiling C object 'drivers/a715181@@rte_net_softnic@sha/meson-generated_.._rte_net_softnic.pmd.c.o'.
[1905/2733] Compiling C object 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_mbox.c.o'.
[1906/2733] Compiling C object 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_ctrlq.c.o'.
FAILED: drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_ctrlq.c.o
clang -Idrivers/net/sssnic/base/a9cdf24@@sssnic_base@sta -Idrivers/net/sssnic/base -I../drivers/net/sssnic/base -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/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/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/ethdev -I../lib/ethdev -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/linux -Ilib/pci -I../lib/pci -Xclang -fcolor-diagnostics -pipe -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-prototypes -Wnested-externs -Wol
d-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -MD -MQ 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_ctrlq.c.o' -MF 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_ctrlq.c.o.d' -o 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_ctrlq.c.o' -c ../drivers/net/sssnic/base/sssnic_ctrlq.c
../drivers/net/sssnic/base/sssnic_ctrlq.c:360:41: error: variable 'cmd_len' is uninitialized when used here [-Werror,-Wuninitialized]
sssnic_msg_init(&msg, (uint8_t *)&cmd, cmd_len, SSSNIC_SET_ROOT_CTX_CMD,
^~~~~~~
../drivers/net/sssnic/base/sssnic_ctrlq.c:354:18: note: initialize the variable 'cmd_len' to silence this warning
uint32_t cmd_len;
^
= 0
1 error generated.
[1907/2733] Compiling C object 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_exception.c.o'.
[1908/2733] Compiling C object 'drivers/net/sssnic/base/a9cdf24@@sssnic_base@sta/sssnic_api.c.o'.
[1909/2733] Generating rte_net_softnic.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27460/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-29 11:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 11:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 12:12 dpdklab
2023-08-29 12:03 dpdklab
2023-08-29 12:02 dpdklab
2023-08-29 12:01 dpdklab
2023-08-29 12:01 dpdklab
2023-08-29 11:59 dpdklab
2023-08-29 11:58 dpdklab
2023-08-29 11:57 dpdklab
2023-08-29 11:55 dpdklab
2023-08-29 11:54 dpdklab
2023-08-29 11:52 dpdklab
2023-08-29 11:52 dpdklab
2023-08-29 11:51 dpdklab
2023-08-29 11:51 dpdklab
2023-08-29 11:51 dpdklab
2023-08-29 11:50 dpdklab
2023-08-29 11:49 dpdklab
2023-08-29 11:49 dpdklab
2023-08-29 11:49 dpdklab
2023-08-29 11:48 dpdklab
2023-08-29 11:48 dpdklab
2023-08-29 11:47 dpdklab
2023-08-29 11:46 dpdklab
2023-08-29 11:46 dpdklab
2023-08-29 11:46 dpdklab
2023-08-29 11:44 dpdklab
2023-08-29 11:42 dpdklab
2023-08-29 11:41 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=64eddd29.920a0220.ee68d.5d81SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=wanry@3snic.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).