automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw123849-123870 [PATCH] [v5, 22/22] hash: convert RTE_LOGTYPE_HASH to dynamic type
Date: Wed, 15 Feb 2023 20:27:10 +0000 (UTC)	[thread overview]
Message-ID: <20230215202710.95EB3600E5@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4300 bytes --]

Test-Label: iol-aarch64-unit-testing
Test-Status: WARNING
http://dpdk.org/patch/123870

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, February 14 2023 02:19:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39d469a7eb4f157923be73aea0b0cc1015860ca7

123849-123870 --> testing fail

Test environment and result as below:

+----------------------+------------------------------+---------------------------+--------------+
|     Environment      | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | lpm_autotest |
+======================+==============================+===========================+==============+
| Debian 11            | FAIL                         | FAIL                      | SKIPPED      |
+----------------------+------------------------------+---------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED                      | SKIPPED                   | FAIL         |
+----------------------+------------------------------+---------------------------+--------------+

==== 20 line log output for Ubuntu 20.04 ARM SVE (lpm_autotest): ====
[141/637] Compiling C object 'lib/76b5a35@@rte_cmdline@sta/cmdline_cmdline_rdline.c.o'.
[142/637] Linking static target lib/librte_cmdline.a.
[143/637] Compiling C object 'lib/76b5a35@@rte_hash@sta/hash_rte_hash_crc.c.o'.
[144/637] Compiling C object 'lib/76b5a35@@rte_hash@sta/hash_rte_fbk_hash.c.o'.
FAILED: lib/76b5a35@@rte_hash@sta/hash_rte_fbk_hash.c.o
gcc-10 -Ilib/76b5a35@@rte_hash@sta -Ilib -I../lib -Ilib/hash -I../lib/hash -I. -I../ -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/arm/include -I../lib/eal/arm/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC -march=armv8.2-a+crypto+sve -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.hash -MD -MQ 'lib/76b5a35@@rte_hash@sta/hash_rte_fbk_hash.c.o' -MF 'lib/76b5a35@@rte_hash@sta/hash_rte_fbk_hash.c.o.d' -o 'lib/76b5a35@@rte_hash@sta/hash_rte_fbk_hash.c.o' -c ../lib/hash/rte_fbk_hash.c
../lib/hash/rte_fbk_hash.c: In function 'rte_fbk_hash_create':
../lib/hash/rte_fbk_hash.c:137:6: error: implicit declaration of function 'rte_cpu_get_flag_enabled' [-Werror=implicit-function-declaration]
137 |  if (rte_cpu_get_flag_enabled(RTE_CPUFLAG_CRC32))
|      ^~~~~~~~~~~~~~~~~~~~~~~~
../lib/hash/rte_fbk_hash.c:137:6: error: nested extern declaration of 'rte_cpu_get_flag_enabled' [-Werror=nested-externs]
../lib/hash/rte_fbk_hash.c:137:31: error: 'RTE_CPUFLAG_CRC32' undeclared (first use in this function)
137 |  if (rte_cpu_get_flag_enabled(RTE_CPUFLAG_CRC32))
|                               ^~~~~~~~~~~~~~~~~
../lib/hash/rte_fbk_hash.c:137:31: note: each undeclared identifier is reported only once for each function it appears in
cc1: all warnings being treated as errors
[145/637] Generating eal.sym_chk with a meson_exe.py custom command.
[146/637] Compiling C object 'lib/76b5a35@@rte_ethdev@sta/ethdev_rte_ethdev.c.o'.
[147/637] Generating cmdline.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====

Debian 11
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2023-02-15 20:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230215202710.95EB3600E5@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=stephen@networkplumber.org \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).