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,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: |FAILURE| pw137149-137169 [PATCH] [v5,22/22] net/virtio: use mbuf de
Date: Sat, 24 Feb 2024 02:37:41 -0800 (PST)	[thread overview]
Message-ID: <65d9c6f5.050a0220.abbb7.5237SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/137169

_Testing issues_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Saturday, February 24 2024 08:22:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137149-137169 --> testing fail

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Debian 11 (Buster) (ARM)               | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE                   | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | FAIL               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | FAIL               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | FAIL               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | FAIL               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | FAIL               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | FAIL               |
+----------------------------------------+--------------------+

==== 20 line log output for CentOS Stream 9 (ARM) (dpdk_meson_compile): ====
from ../drivers/net/hns3/hns3_rxtx_vec.c:6:
../lib/mbuf/rte_mbuf.h:141:38: note: expected 'struct rte_mbuf *' but argument is of type 'struct rte_mbuf **'
141 | rte_mbuf_rearm_data(struct rte_mbuf *m)
|                     ~~~~~~~~~~~~~~~~~^
In file included from ../drivers/net/hns3/hns3_rxtx_vec.c:13:
../drivers/net/hns3/hns3_rxtx_vec_neon.h:255:38: error: passing argument 1 of 'rte_mbuf_rearm_data' from incompatible pointer type [-Werror=incompatible-pointer-types]
255 |                 *rte_mbuf_rearm_data(&sw_ring[pos + 3].mbuf) =
|                                      ^~~~~~~~~~~~~~~~~~~~~~
|                                      |
|                                      struct rte_mbuf **
In file included from ../lib/net/rte_ether.h:22,
from ../lib/ethdev/rte_eth_ctrl.h:10,
from ../lib/ethdev/rte_ethdev.h:1454,
from ../lib/ethdev/ethdev_driver.h:25,
from ../drivers/net/hns3/hns3_rxtx_vec.c:6:
../lib/mbuf/rte_mbuf.h:141:38: note: expected 'struct rte_mbuf *' but argument is of type 'struct rte_mbuf **'
141 | rte_mbuf_rearm_data(struct rte_mbuf *m)
|                     ~~~~~~~~~~~~~~~~~^
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

Debian 11 (Buster) (ARM)
	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)

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

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

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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-24 10:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 10:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-24 10:36 dpdklab
2024-02-24 10:35 dpdklab
2024-02-24 10:34 dpdklab
2024-02-24 10:21 dpdklab
2024-02-24 10:20 dpdklab
2024-02-24 10:20 dpdklab
2024-02-24 10:19 dpdklab
2024-02-24 10:15 dpdklab
2024-02-24 10:15 dpdklab
2024-02-24 10:15 dpdklab
2024-02-24 10:14 dpdklab
2024-02-24 10:14 dpdklab
2024-02-24 10:12 dpdklab
2024-02-24 10:11 dpdklab
2024-02-24 10:10 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=65d9c6f5.050a0220.abbb7.5237SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=roretzla@linux.microsoft.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).