automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw134192-134229 [PATCH] [43/43] vdpa/sfc: use rte strerror
Date: Tue, 14 Nov 2023 01:34:37 -0800 (PST)	[thread overview]
Message-ID: <65533f2d.170a0220.7530.a940SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/134229

_Testing issues_

Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tuesday, November 14 2023 08:25:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:737faa1b4331f6395bc3a665159a489f404e6052

134192-134229 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| Debian Buster       | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+
| openSUSE Leap 15    | FAIL           |
+---------------------+----------------+
| Ubuntu 22.04        | FAIL           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+

==== 20 line log output for Ubuntu 22.04 (dpdk_unit_test): ====
../lib/telemetry/telemetry.c: In function 'socket_listener':
../lib/telemetry/telemetry.c:439:25: error: ignoring return value of 'strerror_r' declared with attribute 'warn_unused_result' [-Werror=unused-result]
439 |                         strerror_r(rc, err_buf, sizeof(err_buf));
|                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c: In function 'create_socket':
../lib/telemetry/telemetry.c:479:17: error: ignoring return value of 'strerror_r' declared with attribute 'warn_unused_result' [-Werror=unused-result]
479 |                 strerror_r(errno, err_buf, sizeof(err_buf));
|                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c:510:25: error: ignoring return value of 'strerror_r' declared with attribute 'warn_unused_result' [-Werror=unused-result]
510 |                         strerror_r(errno, err_buf, sizeof(err_buf));
|                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c:518:17: error: ignoring return value of 'strerror_r' declared with attribute 'warn_unused_result' [-Werror=unused-result]
518 |                 strerror_r(errno, err_buf, sizeof(err_buf));
|                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/telemetry/telemetry.c: In function 'telemetry_legacy_init':
../lib/telemetry/telemetry.c:567:17: error: ignoring return value of 'strerror_r' declared with attribute 'warn_unused_result' [-Werror=unused-result]
567 |                 strerror_r(rc, err_buf, sizeof(err_buf));
|                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28369/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-11-14  9:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  9:34 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-14  9:42 dpdklab
2023-11-14  9:41 dpdklab
2023-11-14  9:40 dpdklab
2023-11-14  9:40 dpdklab
2023-11-14  9:39 dpdklab
2023-11-14  9:39 dpdklab
2023-11-14  9:39 dpdklab
2023-11-14  9:38 dpdklab
2023-11-14  9:38 dpdklab
2023-11-14  9:38 dpdklab
2023-11-14  9:37 dpdklab
2023-11-14  9:37 dpdklab
2023-11-14  9:37 dpdklab
2023-11-14  9:37 dpdklab
2023-11-14  9:37 dpdklab
2023-11-14  9:37 dpdklab
2023-11-14  9:36 dpdklab
2023-11-14  9:36 dpdklab
2023-11-14  9:36 dpdklab
2023-11-14  9:36 dpdklab
2023-11-14  9:36 dpdklab
2023-11-14  9:35 dpdklab
2023-11-14  9:35 dpdklab
2023-11-14  9:35 dpdklab
2023-11-14  9:35 dpdklab
2023-11-14  9:34 dpdklab
2023-11-14  9:34 dpdklab
2023-11-14  9:34 dpdklab
2023-11-14  9:33 dpdklab
2023-11-14  9:33 dpdklab
2023-11-14  9:32 dpdklab
2023-11-14  9:32 dpdklab
2023-11-14  9:32 dpdklab
2023-11-14  9:32 dpdklab
2023-11-14  9:32 dpdklab
2023-11-14  9:32 dpdklab
2023-11-14  9:31 dpdklab
2023-11-14  9:31 dpdklab
2023-11-14  9:30 dpdklab
2023-11-14  9:24 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=65533f2d.170a0220.7530.a940SMTPIN_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).