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
Subject: |WARNING| pw143759 [PATCH] fib: network byte order IPv4 lookup
Date: Sat, 07 Sep 2024 07:30:54 -0700 (PDT)	[thread overview]
Message-ID: <66dc639e.050a0220.305aae.52fdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906170649.1325254-1-vladimir.medvedkin@intel.com>

Test-Label: iol-unit-arm64-testing
Test-Status: WARNING
http://dpdk.org/patch/143759

_Testing issues_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Friday, September 06 2024 17:06:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143759 --> testing issues

Upstream job id: Generic-Unit-Test-DPDK#259686

Test environment and result as below:

+-----------------------------+----------------+------------------------------+--------------+---------------------------+
|         Environment         | dpdk_unit_test | cryptodev_sw_snow3g_autotest | lpm_autotest | cryptodev_sw_zuc_autotest |
+=============================+================+==============================+==============+===========================+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| CentOS Stream 9 (ARM)       | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Debian 11 (Buster) (ARM)    | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora 37 (ARM)             | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora 38 (ARM Clang)       | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora 38 (ARM)             | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora 39 (ARM Clang)       | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora 39 (ARM)             | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora 40 (ARM)             | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Fedora 40 (ARM Clang)       | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| RHEL9 (ARM)                 | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 20.04 (ARM)          | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 24.04 (ARM)          | WARN           | SKIPPED                      | SKIPPED      | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Debian 12 (arm)             | SKIPPED        | WARN                         | SKIPPED      | WARN                      |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | SKIPPED                      | PASS         | SKIPPED                   |
+-----------------------------+----------------+------------------------------+--------------+---------------------------+

==== 20 line log output for Debian 12 (arm) (cryptodev_sw_zuc_autotest): ====
[518/3215] Linking static target lib/librte_node.a
[519/3215] Linking static target drivers/libtmp_rte_common_cpt.a
[520/3215] Generating drivers/rte_common_cpt.pmd.c with a custom command
[521/3215] Compiling C object drivers/librte_common_cpt.a.p/meson-generated_.._rte_common_cpt.pmd.c.o
[522/3215] Linking static target drivers/librte_common_cpt.a
[523/3215] Generating lib/node.sym_chk with a custom command (wrapped by meson to capture output)
[524/3215] Linking target lib/librte_node.so.25.0
[525/3215] Compiling C object drivers/librte_common_cpt.so.25.0.p/meson-generated_.._rte_common_cpt.pmd.c.o
[526/3215] Compiling C object lib/librte_fib.a.p/fib_dir24_8.c.o
FAILED: lib/librte_fib.a.p/fib_dir24_8.c.o
ccache cc -Ilib/librte_fib.a.p -Ilib -I../lib -Ilib/fib -I../lib/fib -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 -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/rib -I../lib/rib -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -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 -march=armv8-a+crc+crypto -fP
 IC -march=armv8-a+crc -moutline-atomics -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.fib -MD -MQ lib/librte_fib.a.p/fib_dir24_8.c.o -MF lib/librte_fib.a.p/fib_dir24_8.c.o.d -o lib/librte_fib.a.p/fib_dir24_8.c.o -c ../lib/fib/dir24_8.c
../lib/fib/dir24_8.c: In function 'get_vector_fn':
../lib/fib/dir24_8.c:71:54: error: unused parameter 'be_addr' [-Werror=unused-parameter]
71 | get_vector_fn(enum rte_fib_dir24_8_nh_sz nh_sz, bool be_addr)
|                                                      ^
cc1: all warnings being treated as errors
[527/3215] Compiling C object drivers/libtmp_rte_common_dpaax.a.p/common_dpaax_dpaax_iova_table.c.o
[528/3215] Generating drivers/rte_common_cpt.sym_chk with a custom command (wrapped by meson to capture output)
[529/3215] Generating lib/pipeline.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====

32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

CentOS Stream 9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Debian 11 (Buster) (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 20.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 24.04 (ARM)
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

Debian 12 (arm)
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-07 14:30 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906170649.1325254-1-vladimir.medvedkin@intel.com>
2024-09-06 16:51 ` |SUCCESS| " qemudev
2024-09-06 16:55 ` qemudev
2024-09-06 17:07 ` checkpatch
2024-09-06 17:44 ` |FAILURE| " 0-day Robot
2024-09-06 21:56 ` |SUCCESS| " dpdklab
2024-09-06 22:10 ` dpdklab
2024-09-06 22:13 ` dpdklab
2024-09-06 22:13 ` |PENDING| " dpdklab
2024-09-06 22:26 ` |SUCCESS| " dpdklab
2024-09-06 22:27 ` dpdklab
2024-09-06 22:32 ` dpdklab
2024-09-06 23:00 ` dpdklab
2024-09-06 23:00 ` dpdklab
2024-09-06 23:16 ` |PENDING| " dpdklab
2024-09-06 23:35 ` |SUCCESS| " dpdklab
2024-09-06 23:42 ` |PENDING| " dpdklab
2024-09-06 23:49 ` dpdklab
2024-09-06 23:59 ` dpdklab
2024-09-07  0:09 ` |SUCCESS| " dpdklab
2024-09-07  1:32 ` |FAILURE| " dpdklab
2024-09-07  1:34 ` |WARNING| " dpdklab
2024-09-07  2:24 ` |FAILURE| " dpdklab
2024-09-07  3:04 ` dpdklab
2024-09-07  4:31 ` |SUCCESS| " dpdklab
2024-09-07  4:48 ` |FAILURE| " dpdklab
2024-09-07  4:48 ` dpdklab
2024-09-07  5:11 ` |WARNING| " dpdklab
2024-09-07  5:17 ` |SUCCESS| " dpdklab
2024-09-07  5:35 ` |WARNING| " dpdklab
2024-09-07  9:00 ` |SUCCESS| " dpdklab
2024-09-07  9:05 ` dpdklab
2024-09-07  9:24 ` dpdklab
2024-09-07  9:29 ` dpdklab
2024-09-07  9:37 ` dpdklab
2024-09-07  9:42 ` dpdklab
2024-09-07  9:47 ` dpdklab
2024-09-07  9:52 ` dpdklab
2024-09-07 10:34 ` dpdklab
2024-09-07 11:00 ` dpdklab
2024-09-07 13:44 ` |FAILURE| " dpdklab
2024-09-07 14:04 ` dpdklab
2024-09-07 14:30 ` dpdklab [this message]
2024-09-07 14:39 ` |WARNING| " dpdklab
2024-09-07 14:46 ` |FAILURE| " dpdklab
2024-09-07 14:46 ` dpdklab
2024-09-07 14:48 ` dpdklab
2024-09-07 14:49 ` dpdklab
2024-09-07 14:50 ` dpdklab
2024-09-07 14:52 ` dpdklab
2024-09-07 14:52 ` dpdklab
2024-09-07 14:54 ` dpdklab
2024-09-07 14:54 ` dpdklab
2024-09-07 14:55 ` dpdklab
2024-09-07 14:56 ` dpdklab
2024-09-07 14:57 ` dpdklab
2024-09-07 14:57 ` dpdklab
2024-09-07 14:57 ` dpdklab
2024-09-07 14:59 ` dpdklab
2024-09-07 14:59 ` dpdklab
2024-09-07 15:00 ` dpdklab
2024-09-07 15:00 ` dpdklab
2024-09-07 15:01 ` dpdklab
2024-09-07 15:02 ` dpdklab
2024-09-07 15:03 ` dpdklab
2024-09-07 15:04 ` dpdklab
2024-09-07 15:04 ` dpdklab
2024-09-07 15:04 ` dpdklab
2024-09-07 15:05 ` dpdklab
2024-09-07 15:05 ` dpdklab
2024-09-07 15:07 ` dpdklab
2024-09-07 15:38 ` dpdklab
2024-09-07 16:07 ` dpdklab
2024-09-07 16:09 ` dpdklab
2024-09-07 16:09 ` dpdklab
2024-09-08 10:38 ` |SUCCESS| " dpdklab
2024-09-08 11:06 ` dpdklab
2024-09-17  2:33 ` dpdklab
2024-09-17  2:52 ` dpdklab
2024-09-17  3:03 ` dpdklab
2024-09-22  0:00 ` 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=66dc639e.050a0220.305aae.52fdSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).