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,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |FAILURE| pw140927-140931 [PATCH] [v4,5/5] vhost: manage FD with epo
Date: Wed, 12 Jun 2024 18:22:40 -0700 (PDT)	[thread overview]
Message-ID: <666a49e0.050a0220.4c8b.153bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240611133957.72032-6-maxime.coquelin@redhat.com>

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

_Testing issues_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Tuesday, June 11 2024 13:39:57 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33

140927-140931 --> testing issues

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM)                     | FAIL               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| RHEL9 (ARM)                            | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+
| Fedora 39 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+

==== 20 line log output for Ubuntu 24.04 (ARM) (dpdk_meson_compile): ====
In function 'memcpy',
inlined from 'pcapng_add_option' at ../lib/pcapng/rte_pcapng.c:131:2,
inlined from 'rte_pcapng_add_interface' at ../lib/pcapng/rte_pcapng.c:308:8:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: error: argument 2 null where non-null expected [-Werror=nonnull]
29 |   return __builtin___memcpy_chk (__dest, __src, __len,
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 |                                  __glibc_objsize0 (__dest));
|                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to built-in function '__builtin___memcpy_chk'
In function 'memcpy',
inlined from 'pcapng_add_option' at ../lib/pcapng/rte_pcapng.c:131:2,
inlined from 'rte_pcapng_write_stats' at ../lib/pcapng/rte_pcapng.c:371:9:
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: error: argument 2 null where non-null expected [-Werror=nonnull]
29 |   return __builtin___memcpy_chk (__dest, __src, __len,
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
30 |                                  __glibc_objsize0 (__dest));
|                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/aarch64-linux-gnu/bits/string_fortified.h:29:10: note: in a call to built-in function '__builtin___memcpy_chk'
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

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

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

Ubuntu 24.04 (ARM)
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

Ubuntu 22.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.0

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

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

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-13  1:35 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240611133957.72032-6-maxime.coquelin@redhat.com>
2024-06-11 13:14 ` |SUCCESS| pw140927-140931 [PATCH v4 5/5] vhost: manage FD with epoll qemudev
2024-06-11 13:19 ` qemudev
2024-06-11 13:42 ` |SUCCESS| pw140931 " checkpatch
2024-06-11 14:44 ` 0-day Robot
2024-06-11 18:42 ` |SUCCESS| pw140927-140931 [PATCH] [v4,5/5] vhost: manage FD with epo dpdklab
2024-06-11 18:47 ` dpdklab
2024-06-11 18:50 ` dpdklab
2024-06-11 18:51 ` dpdklab
2024-06-11 18:54 ` dpdklab
2024-06-11 19:05 ` dpdklab
2024-06-13  1:10 ` dpdklab
2024-06-13  1:12 ` dpdklab
2024-06-13  1:12 ` |FAILURE| " dpdklab
2024-06-13  1:12 ` |SUCCESS| " dpdklab
2024-06-13  1:13 ` dpdklab
2024-06-13  1:13 ` dpdklab
2024-06-13  1:14 ` dpdklab
2024-06-13  1:14 ` |FAILURE| " dpdklab
2024-06-13  1:14 ` |SUCCESS| " dpdklab
2024-06-13  1:15 ` |FAILURE| " dpdklab
2024-06-13  1:16 ` |SUCCESS| " dpdklab
2024-06-13  1:16 ` |FAILURE| " dpdklab
2024-06-13  1:16 ` |SUCCESS| " dpdklab
2024-06-13  1:16 ` dpdklab
2024-06-13  1:16 ` dpdklab
2024-06-13  1:17 ` dpdklab
2024-06-13  1:17 ` dpdklab
2024-06-13  1:18 ` dpdklab
2024-06-13  1:18 ` dpdklab
2024-06-13  1:19 ` dpdklab
2024-06-13  1:19 ` dpdklab
2024-06-13  1:19 ` |FAILURE| " dpdklab
2024-06-13  1:20 ` |SUCCESS| " dpdklab
2024-06-13  1:20 ` dpdklab
2024-06-13  1:20 ` |FAILURE| " dpdklab
2024-06-13  1:20 ` dpdklab
2024-06-13  1:20 ` dpdklab
2024-06-13  1:21 ` dpdklab
2024-06-13  1:21 ` |SUCCESS| " dpdklab
2024-06-13  1:21 ` |FAILURE| " dpdklab
2024-06-13  1:21 ` dpdklab
2024-06-13  1:21 ` |SUCCESS| " dpdklab
2024-06-13  1:21 ` |FAILURE| " dpdklab
2024-06-13  1:22 ` dpdklab
2024-06-13  1:22 ` dpdklab
2024-06-13  1:22 ` |SUCCESS| " dpdklab
2024-06-13  1:22 ` |FAILURE| " dpdklab
2024-06-13  1:22 ` dpdklab
2024-06-13  1:22 ` dpdklab [this message]
2024-06-13  1:22 ` dpdklab
2024-06-13  1:22 ` dpdklab
2024-06-13  1:23 ` |SUCCESS| " dpdklab
2024-06-13  1:23 ` |FAILURE| " dpdklab
2024-06-13  1:23 ` dpdklab
2024-06-13  1:23 ` dpdklab
2024-06-13  1:23 ` dpdklab
2024-06-13  1:23 ` |SUCCESS| " dpdklab
2024-06-13  1:23 ` |FAILURE| " dpdklab
2024-06-13  1:23 ` dpdklab
2024-06-13  1:23 ` dpdklab
2024-06-13  1:23 ` dpdklab
2024-06-13  1:23 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:24 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:25 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:26 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:27 ` dpdklab
2024-06-13  1:28 ` dpdklab
2024-06-13  1:28 ` dpdklab
2024-06-13  1:28 ` dpdklab
2024-06-13  1:28 ` dpdklab
2024-06-13  1:28 ` dpdklab
2024-06-13  1:28 ` |SUCCESS| " 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=666a49e0.050a0220.4c8b.153bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=maxime.coquelin@redhat.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).