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:36:13 -0800 (PST)	[thread overview]
Message-ID: <65533f8d.2e0a0220.d842b.4e86SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-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_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile     | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | FAIL               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | FAIL               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | FAIL               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | FAIL               |
+----------------------------------------+--------------------+

==== 20 line log output for Fedora 38 (ARM Clang) (dpdk_meson_compile): ====
rte_strerror(errno));
^~~~~~~~~~~~~~~~~~~
../lib/vhost/vhost.h:680:40: note: expanded from macro 'VHOST_LOG_CONFIG'
"VHOST_CONFIG: (%s) " fmt, prefix, ##args)
~~~            ^~~~
../lib/vhost/vduse.c:403:5: error: call to undeclared function 'rte_strerror'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
rte_strerror(errno));
^
../lib/vhost/vduse.c:403:5: error: format specifies type 'char *' but the argument has type 'int' [-Werror,-Wformat]
rte_strerror(errno));
^~~~~~~~~~~~~~~~~~~
../lib/vhost/vhost.h:680:40: note: expanded from macro 'VHOST_LOG_CONFIG'
"VHOST_CONFIG: (%s) " fmt, prefix, ##args)
~~~            ^~~~
../lib/vhost/vduse.c:456:22: error: call to undeclared function 'rte_strerror'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
VDUSE_CTRL_PATH, rte_strerror(errno));
^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
ninja: build stopped: subcommand failed.
==== End log output ====

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 SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

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

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  9:36 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: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: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=65533f8d.2e0a0220.d842b.4e86SMTPIN_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).