From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Wenjing Qiao <wenjing.qiao@intel.com>
Subject: |FAILURE| pw135496-135497 [PATCH] [2/2] net/cpfl: add TDI to flow en
Date: Fri, 22 Dec 2023 18:39:38 -0800 (PST) [thread overview]
Message-ID: <6586486a.250a0220.21ea1.0951SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/135497
_Testing issues_
Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Friday, December 22 2023 10:08:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135496-135497 --> testing fail
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| FreeBSD 13 | FAIL |
+---------------------+--------------------+
==== 20 line log output for FreeBSD 13 (dpdk_meson_compile): ====
[877/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82540.c.o
[878/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82541.c.o
[879/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82542.c.o
[880/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82543.c.o
[881/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82571.c.o
[882/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_82575.c.o
[883/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_api.c.o
[884/1814] Compiling C object drivers/libtmp_rte_net_cpfl.a.p/net_cpfl_cpfl_tdi.c.o
FAILED: drivers/libtmp_rte_net_cpfl.a.p/net_cpfl_cpfl_tdi.c.o
ccache cc -Idrivers/libtmp_rte_net_cpfl.a.p -Idrivers -I../drivers -Idrivers/net/cpfl -I../drivers/net/cpfl -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 -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Idrivers/common/idpf -I../drivers/common/idpf -Idrivers/common/iavf -I../drivers/common/iavf -I/usr/local/include -fcolor-diagnostics -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O
3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -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 -DCC_AVX512_SUPPORT -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.cpfl -DRTE_ANNOTATE_LOCKS -Wthread-safety -MD -MQ drivers/libtmp_rte_net_cpfl.a.p/net_cpfl_cpfl_tdi.c.o -MF drivers/libtmp_rte_net_cpfl.a.p/net_cpfl_cpfl_tdi.c.o.d -o drivers/libtmp_rte_net_cpfl.a.p/net_cpfl_cpfl_tdi.c.o -c ../drivers/net/cpfl/cpfl_tdi.c
../drivers/net/cpfl/cpfl_tdi.c:4:10: fatal error: 'asm-generic/errno-base.h' file not found
#include <asm-generic/errno-base.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[885/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_i210.c.o
[886/1814] Compiling C object drivers/net/e1000/base/libe1000_base.a.p/e1000_ich8lan.c.o
[887/1814] Generating drivers/rte_net_cxgbe.pmd.c with a custom command
[888/1814] Compiling C object drivers/libtmp_rte_net_cpfl.a.p/net_cpfl_cpfl_tdi_parser.c.o
[889/1814] 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 ====
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28722/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-23 2:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 2:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-23 4:23 dpdklab
2023-12-23 4:12 dpdklab
2023-12-23 4:08 dpdklab
2023-12-23 4:07 dpdklab
2023-12-23 4:05 dpdklab
2023-12-23 4:04 dpdklab
2023-12-23 4:04 dpdklab
2023-12-23 4:03 dpdklab
2023-12-23 4:02 dpdklab
2023-12-23 4:01 dpdklab
2023-12-23 3:54 dpdklab
2023-12-23 3:53 dpdklab
2023-12-23 3:48 dpdklab
2023-12-23 3:46 dpdklab
2023-12-23 3:44 dpdklab
2023-12-23 3:42 dpdklab
2023-12-23 3:39 dpdklab
2023-12-23 3:38 dpdklab
2023-12-23 3:38 dpdklab
2023-12-23 3:37 dpdklab
2023-12-23 2:49 dpdklab
2023-12-23 2:39 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=6586486a.250a0220.21ea1.0951SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=wenjing.qiao@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).