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| pw134280-134316 [PATCH] [v2,43/43] vdpa/sfc: use rte strer
Date: Tue, 14 Nov 2023 04:14:47 -0800 (PST) [thread overview]
Message-ID: <655364b7.170a0220.14cac.b157SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/134316
_Testing issues_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tuesday, November 14 2023 11:24:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:737faa1b4331f6395bc3a665159a489f404e6052
134280-134316 --> testing fail
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | FAIL |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | FAIL |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
==== 20 line log output for Ubuntu 20.04 aarch32 GCC Cross Compile (dpdk_meson_compile): ====
../lib/telemetry/telemetry.c: In function 'socket_listener':
../lib/telemetry/telemetry.c:439:10: error: ignoring return value of 'strerror_r', declared with attribute warn_unused_result [-Werror=unused-result]
439 | (void)strerror_r(rc, err_buf, sizeof(err_buf));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c: In function 'create_socket':
../lib/telemetry/telemetry.c:479:9: error: ignoring return value of 'strerror_r', declared with attribute warn_unused_result [-Werror=unused-result]
479 | (void)strerror_r(errno, err_buf, sizeof(err_buf));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c:510:10: error: ignoring return value of 'strerror_r', declared with attribute warn_unused_result [-Werror=unused-result]
510 | (void)strerror_r(errno, err_buf, sizeof(err_buf));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c:518:9: error: ignoring return value of 'strerror_r', declared with attribute warn_unused_result [-Werror=unused-result]
518 | (void)strerror_r(errno, err_buf, sizeof(err_buf));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c: In function 'telemetry_legacy_init':
../lib/telemetry/telemetry.c:567:9: error: ignoring return value of 'strerror_r', declared with attribute warn_unused_result [-Werror=unused-result]
567 | (void)strerror_r(rc, err_buf, sizeof(err_buf));
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28376/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-14 12:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 12:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-14 14:59 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:27 dpdklab
2023-11-14 12:54 dpdklab
2023-11-14 12:45 dpdklab
2023-11-14 12:38 dpdklab
2023-11-14 12:34 dpdklab
2023-11-14 12:34 dpdklab
2023-11-14 12:33 dpdklab
2023-11-14 12:33 dpdklab
2023-11-14 12:33 dpdklab
2023-11-14 12:32 dpdklab
2023-11-14 12:30 dpdklab
2023-11-14 12:30 dpdklab
2023-11-14 12:30 dpdklab
2023-11-14 12:29 dpdklab
2023-11-14 12:29 dpdklab
2023-11-14 12:28 dpdklab
2023-11-14 12:28 dpdklab
2023-11-14 12:25 dpdklab
2023-11-14 12:23 dpdklab
2023-11-14 12:23 dpdklab
2023-11-14 12:21 dpdklab
2023-11-14 12:20 dpdklab
2023-11-14 12:20 dpdklab
2023-11-14 12:19 dpdklab
2023-11-14 12:19 dpdklab
2023-11-14 12:15 dpdklab
2023-11-14 12:15 dpdklab
2023-11-14 12:15 dpdklab
2023-11-14 12:15 dpdklab
2023-11-14 12:14 dpdklab
2023-11-14 12:13 dpdklab
2023-11-14 12:13 dpdklab
2023-11-14 12:13 dpdklab
2023-11-14 12:13 dpdklab
2023-11-14 12:12 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=655364b7.170a0220.14cac.b157SMTPIN_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).