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, Jie Hai <haijie1@huawei.com>
Subject: |FAILURE| pw133485-133491 [PATCH] [9/9] app/testpmd: add RSS hash al
Date: Fri, 27 Oct 2023 06:38:34 -0700 (PDT)	[thread overview]
Message-ID: <653bbd5a.020a0220.845da.2e40SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Friday, October 27 2023 09:28:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:656dfad43136ef43f4315ab6ed45b78b68c287a7

133485-133491 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Ubuntu 22.04 (dpdk_unit_test): ====
In file included from ../lib/ethdev/rte_ethdev.c:30:
../lib/ethdev/rte_ethdev.c: In function 'rte_eth_dev_configure':
../lib/ethdev/rte_ethdev.h:181:57: error: format '%lx' expects a matching 'long unsigned int' argument [-Werror=format=]
181 |         rte_log(RTE_LOG_ ## level, rte_eth_dev_logtype, "" __VA_ARGS__)
|                                                         ^~
../lib/ethdev/rte_ethdev.c:1518:17: note: in expansion of macro 'RTE_ETHDEV_LOG'
1518 |                 RTE_ETHDEV_LOG(ERR,
|                 ^~~~~~~~~~~~~~
../lib/ethdev/rte_ethdev.c: In function 'rte_eth_dev_rss_hash_update':
../lib/ethdev/rte_ethdev.h:181:57: error: format '%lx' expects a matching 'long unsigned int' argument [-Werror=format=]
181 |         rte_log(RTE_LOG_ ## level, rte_eth_dev_logtype, "" __VA_ARGS__)
|                                                         ^~
../lib/ethdev/rte_ethdev.c:4728:17: note: in expansion of macro 'RTE_ETHDEV_LOG'
4728 |                 RTE_ETHDEV_LOG(ERR,
|                 ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
[129/2743] Compiling C object 'lib/76b5a35@@rte_ethdev@sta/ethdev_rte_mtr.c.o'.
[130/2743] Compiling C object 'lib/76b5a35@@rte_ethdev@sta/ethdev_rte_flow.c.o'.
[131/2743] Generating eal.sym_chk with a meson_exe.py custom command.
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

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

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

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-27 13:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 13:38 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-27 14:08 dpdklab
2023-10-27 13:55 dpdklab
2023-10-27 13:47 dpdklab
2023-10-27 13:47 dpdklab
2023-10-27 13:47 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:45 dpdklab
2023-10-27 13:45 dpdklab
2023-10-27 13:45 dpdklab
2023-10-27 13:45 dpdklab
2023-10-27 13:44 dpdklab
2023-10-27 13:44 dpdklab
2023-10-27 13:39 dpdklab
2023-10-27 13:39 dpdklab
2023-10-27 13:39 dpdklab
2023-10-27 13:39 dpdklab
2023-10-27 13:39 dpdklab
2023-10-27 13:38 dpdklab
2023-10-27 13:38 dpdklab
2023-10-27 13:38 dpdklab
2023-10-27 13:38 dpdklab
2023-10-27 13:38 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:33 dpdklab
2023-10-27 13:25 dpdklab
2023-10-27 13:25 dpdklab
2023-10-27 13:23 dpdklab
2023-10-27 13:20 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=653bbd5a.020a0220.845da.2e40SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=haijie1@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).