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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw137363 [PATCH] lib/hash: add SipHash function
Date: Tue, 27 Feb 2024 16:57:21 -0800 (PST)	[thread overview]
Message-ID: <65de84f1.170a0220.885dc.0c9bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227174012.343004-1-stephen@networkplumber.org>

Test-Label: iol-unit-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/137363

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, February 27 2024 17:39:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137363 --> testing fail

Test environment and result as below:

+--------------------------+--------------+---------------------------+------------------------------+----------------+
|       Environment        | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+==============+===========================+==============================+================+
| Ubuntu 20.04 ARM SVE     | FAIL         | SKIPPED                   | SKIPPED                      | SKIPPED        |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Debian 12 (arm)          | SKIPPED      | FAIL                      | FAIL                         | FAIL           |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED      | SKIPPED                   | SKIPPED                      | FAIL           |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Fedora 37 (ARM)          | SKIPPED      | SKIPPED                   | SKIPPED                      | FAIL           |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM)    | SKIPPED      | SKIPPED                   | SKIPPED                      | FAIL           |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Fedora 38 (ARM)          | SKIPPED      | SKIPPED                   | SKIPPED                      | FAIL           |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Ubuntu 20.04 (ARM)       | SKIPPED      | SKIPPED                   | SKIPPED                      | FAIL           |
+--------------------------+--------------+---------------------------+------------------------------+----------------+
| Fedora 38 (ARM Clang)    | SKIPPED      | SKIPPED                   | SKIPPED                      | FAIL           |
+--------------------------+--------------+---------------------------+------------------------------+----------------+

==== 20 line log output for Fedora 38 (ARM Clang) (dpdk_unit_test): ====
../lib/hash/rte_siphash.c:46:42: error: operand of type 'const void' where arithmetic or pointer type is required
return (uint32_t)p[0]       | (uint32_t)p[1] << 8 |
^~~~
../lib/hash/rte_siphash.c:47:14: error: subscript of a pointer to void is a GNU extension [-Werror,-Wgnu-pointer-arith]
(uint32_t)p[2] << 16 | (uint32_t)p[3] << 24;
~^
../lib/hash/rte_siphash.c:47:13: error: operand of type 'const void' where arithmetic or pointer type is required
(uint32_t)p[2] << 16 | (uint32_t)p[3] << 24;
^~~~
../lib/hash/rte_siphash.c:47:37: error: subscript of a pointer to void is a GNU extension [-Werror,-Wgnu-pointer-arith]
(uint32_t)p[2] << 16 | (uint32_t)p[3] << 24;
~^
../lib/hash/rte_siphash.c:47:36: error: operand of type 'const void' where arithmetic or pointer type is required
(uint32_t)p[2] << 16 | (uint32_t)p[3] << 24;
^~~~
9 errors generated.
[174/3119] Generating symbol file 'lib/76b5a35@@rte_net@sha/librte_net.so.24.1.symbols'.
[175/3119] Compiling C object 'lib/76b5a35@@rte_hash@sta/hash_rte_cuckoo_hash.c.o'.
[176/3119] Generating ethdev.sym_chk with a meson_exe.py custom command.
ninja: build stopped: subcommand failed.
==== End log output ====

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

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

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

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

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/29295/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28  0:57 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227174012.343004-1-stephen@networkplumber.org>
2024-02-27 17:40 ` |WARNING| " checkpatch
2024-02-27 17:41 ` |FAILURE| " qemudev
2024-02-27 18:44 ` 0-day Robot
2024-02-27 20:01 ` |SUCCESS| " dpdklab
2024-02-27 20:24 ` dpdklab
2024-02-27 20:37 ` dpdklab
2024-02-27 20:43 ` dpdklab
2024-02-27 20:44 ` dpdklab
2024-02-27 20:48 ` dpdklab
2024-02-27 20:52 ` dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:55 ` dpdklab
2024-02-27 20:56 ` dpdklab
2024-02-27 20:57 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 20:59 ` dpdklab
2024-02-28  0:25 ` |FAILURE| " dpdklab
2024-02-28  0:25 ` dpdklab
2024-02-28  0:25 ` dpdklab
2024-02-28  0:25 ` |SUCCESS| " dpdklab
2024-02-28  0:25 ` |FAILURE| " dpdklab
2024-02-28  0:26 ` dpdklab
2024-02-28  0:26 ` dpdklab
2024-02-28  0:26 ` |SUCCESS| " dpdklab
2024-02-28  0:26 ` |FAILURE| " dpdklab
2024-02-28  0:27 ` |SUCCESS| " dpdklab
2024-02-28  0:27 ` dpdklab
2024-02-28  0:30 ` |FAILURE| " dpdklab
2024-02-28  0:31 ` |SUCCESS| " dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:31 ` dpdklab
2024-02-28  0:32 ` dpdklab
2024-02-28  0:34 ` dpdklab
2024-02-28  0:35 ` dpdklab
2024-02-28  0:35 ` dpdklab
2024-02-28  0:38 ` |FAILURE| " dpdklab
2024-02-28  0:44 ` dpdklab
2024-02-28  0:44 ` |SUCCESS| " dpdklab
2024-02-28  0:45 ` dpdklab
2024-02-28  0:46 ` dpdklab
2024-02-28  0:46 ` |FAILURE| " dpdklab
2024-02-28  0:48 ` |SUCCESS| " dpdklab
2024-02-28  0:48 ` |FAILURE| " dpdklab
2024-02-28  0:49 ` |SUCCESS| " dpdklab
2024-02-28  0:56 ` |FAILURE| " dpdklab
2024-02-28  0:56 ` dpdklab
2024-02-28  0:57 ` dpdklab [this message]
2024-02-28  0:57 ` |SUCCESS| " dpdklab
2024-02-28  0:59 ` |FAILURE| " dpdklab
2024-02-28  1:11 ` dpdklab
2024-02-28  1:16 ` |SUCCESS| " dpdklab
2024-02-28  1:27 ` dpdklab
2024-02-28  1:28 ` dpdklab
2024-02-28  2:22 ` dpdklab
2024-02-28  3:48 ` dpdklab
2024-02-28  9:04 ` dpdklab
2024-02-28 11:45 ` dpdklab
2024-02-28 11:46 ` dpdklab
2024-02-28 18:23 ` dpdklab
2024-02-29  9:14 ` 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=65de84f1.170a0220.885dc.0c9bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).