From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Dengdui Huang <huangdengdui@huawei.com>
Subject: |FAILURE| pw146864-146904 [PATCH] [v4,42/42] vdpa/sfc: use rte strer
Date: Wed, 23 Oct 2024 16:26:41 -0700 (PDT) [thread overview]
Message-ID: <67198631.170a0220.2bd723.3193SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241023082852.2780488-43-huangdengdui@huawei.com>
Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/146904
_Testing issues_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Wednesday, October 23 2024 08:28:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f
146864-146904 --> testing issues
Upstream job id: Generic-VM-DPDK-Compile-Meson#30635
Test environment and result as below:
+--------------+--------------------+
| Environment | dpdk_meson_compile |
+==============+====================+
| FreeBSD 13.4 | FAIL |
+--------------+--------------------+
| FreeBSD 14.1 | FAIL |
+--------------+--------------------+
==== 20 line log output for FreeBSD 14.1 (dpdk_meson_compile): ====
388 | RTE_LOG(l, t, RTE_FMT(RTE_FMT_HEAD(__VA_ARGS__ ,) "\n", \
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
389 | RTE_FMT_TAIL(__VA_ARGS__ ,))); \
| ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
../lib/eal/include/rte_common.h:761:32: note: expanded from macro 'RTE_FMT_TAIL'
761 | #define RTE_FMT_TAIL(fmt, ...) __VA_ARGS__
| ^
../lib/eal/include/rte_common.h:759:39: note: expanded from macro 'RTE_FMT'
759 | #define RTE_FMT(fmt, ...) fmt "%.0s", __VA_ARGS__ ""
| ~~~ ^
../lib/log/rte_log.h:334:32: note: expanded from macro 'RTE_LOG'
334 | RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
| ^~~~~~~~~~~
8 errors generated.
[562/1857] Compiling C object drivers/libtmp_rte_bus_vdev.a.p/bus_vdev_vdev.c.o
[563/1857] Compiling C object drivers/libtmp_rte_common_qat.a.p/common_qat_qat_common.c.o
[564/1857] Compiling C object drivers/libtmp_rte_common_qat.a.p/common_qat_qat_qp.c.o
[565/1857] Generating drivers/rte_common_idpf.sym_chk with a custom command (wrapped by meson to capture output)
[566/1857] Generating lib/pipeline.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====
FreeBSD 13.4
Kernel: 13.4-RELEASE-p1
Compiler: clang 18.1.6
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31620/
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-10-23 23:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023082852.2780488-43-huangdengdui@huawei.com>
2024-10-23 8:02 ` |SUCCESS| pw146864-146904 [PATCH v4 42/42] vdpa/sfc: use rte strerror qemudev
2024-10-23 8:07 ` qemudev
2024-10-23 8:33 ` |SUCCESS| pw146904 " checkpatch
2024-10-23 9:26 ` 0-day Robot
2024-10-23 19:20 ` |SUCCESS| pw146864-146904 [PATCH] [v4,42/42] vdpa/sfc: use rte strer dpdklab
2024-10-23 19:34 ` dpdklab
2024-10-23 19:45 ` dpdklab
2024-10-23 20:13 ` dpdklab
2024-10-23 20:59 ` dpdklab
2024-10-23 21:24 ` dpdklab
2024-10-23 21:54 ` dpdklab
2024-10-23 23:22 ` |FAILURE| " dpdklab
2024-10-23 23:22 ` |PENDING| " dpdklab
2024-10-23 23:26 ` dpdklab [this message]
2024-10-23 23:32 ` |SUCCESS| " dpdklab
2024-10-23 23:37 ` |PENDING| " dpdklab
2024-10-23 23:42 ` |SUCCESS| " dpdklab
2024-10-23 23:57 ` dpdklab
2024-10-24 0:15 ` dpdklab
2024-10-24 1:36 ` |PENDING| " dpdklab
2024-10-24 2:01 ` |WARNING| " dpdklab
2024-10-24 2:08 ` |FAILURE| " dpdklab
2024-10-24 3:08 ` 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=67198631.170a0220.2bd723.3193SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=huangdengdui@huawei.com \
--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).