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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 3a9281f20e36c3ccf49ad421ac99a28a650f220c
Date: Mon,  9 May 2022 00:33:27 +0000 (UTC)	[thread overview]
Message-ID: <20220509003327.3905B600B3@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Testing issues_

Branch: tags/v20.11

3a9281f20e36c3ccf49ad421ac99a28a650f220c --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| Arch Linux          | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 31           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 33           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL 7              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 32           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34 clang     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+

==== 20 line log output for Arch Linux (dpdk_meson_compile): ====
/usr/include/bpf/xsk.h:310:5: note: declared here
310 | int xsk_socket__create(struct xsk_socket **xsk,
|     ^~~~~~~~~~~~~~~~~~
../drivers/net/af_xdp/rte_eth_af_xdp.c:1163:9: error: ‘xsk_socket__delete’ is deprecated: libbpf v0.7+: AF_XDP support deprecated and moved to libxdp [-Werror=deprecated-declarations]
1163 |         xsk_socket__delete(rxq->xsk);
|         ^~~~~~~~~~~~~~~~~~
In file included from ../drivers/net/af_xdp/rte_eth_af_xdp.c:19:
/usr/include/bpf/xsk.h:330:6: note: declared here
330 | void xsk_socket__delete(struct xsk_socket *xsk);
|      ^~~~~~~~~~~~~~~~~~
../drivers/net/af_xdp/rte_eth_af_xdp.c: In function ‘eth_rx_queue_setup’:
../drivers/net/af_xdp/rte_eth_af_xdp.c:1212:9: error: ‘xsk_socket__fd’ is deprecated: libbpf v0.7+: AF_XDP support deprecated and moved to libxdp [-Werror=deprecated-declarations]
1212 |         rxq->fds[0].fd = xsk_socket__fd(rxq->xsk);
|         ^~~
In file included from ../drivers/net/af_xdp/rte_eth_af_xdp.c:19:
/usr/include/bpf/xsk.h:257:5: note: declared here
257 | int xsk_socket__fd(const struct xsk_socket *xsk);
|     ^~~~~~~~~~~~~~
cc1: all warnings being treated as errors
ninja: build stopped: subcommand failed.
==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/19716/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-05-09  0:33 UTC|newest]

Thread overview: 231+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  0:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-15  5:05 dpdklab
2022-08-14  5:14 dpdklab
2022-08-13  5:30 dpdklab
2022-08-12  6:06 dpdklab
2022-08-08  5:11 dpdklab
2022-08-08  5:09 dpdklab
2022-08-08  5:06 dpdklab
2022-08-08  4:48 dpdklab
2022-08-07  5:23 dpdklab
2022-08-07  5:12 dpdklab
2022-08-07  4:52 dpdklab
2022-08-07  4:49 dpdklab
2022-08-06  5:12 dpdklab
2022-08-06  5:07 dpdklab
2022-08-06  4:52 dpdklab
2022-08-06  4:49 dpdklab
2022-08-05  5:45 dpdklab
2022-08-04  5:46 dpdklab
2022-08-04  5:10 dpdklab
2022-08-03  5:22 dpdklab
2022-08-03  5:12 dpdklab
2022-08-02  5:42 dpdklab
2022-08-02  5:33 dpdklab
2022-08-01  5:25 dpdklab
2022-08-01  5:15 dpdklab
2022-07-31  5:13 dpdklab
2022-07-31  5:11 dpdklab
2022-07-30  5:27 dpdklab
2022-07-30  5:16 dpdklab
2022-07-29  5:54 dpdklab
2022-07-29  5:26 dpdklab
2022-07-28  6:16 dpdklab
2022-07-28  5:26 dpdklab
2022-07-27  5:34 dpdklab
2022-07-27  5:29 dpdklab
2022-07-26  6:12 dpdklab
2022-07-26  6:06 dpdklab
2022-07-25  6:17 dpdklab
2022-07-25  5:45 dpdklab
2022-07-24  5:39 dpdklab
2022-07-24  5:39 dpdklab
2022-07-23  5:37 dpdklab
2022-07-23  5:37 dpdklab
2022-07-22  6:07 dpdklab
2022-07-22  5:22 dpdklab
2022-07-21  6:32 dpdklab
2022-07-21  5:36 dpdklab
2022-07-20  6:24 dpdklab
2022-07-20  5:48 dpdklab
2022-07-19  6:00 dpdklab
2022-07-19  5:32 dpdklab
2022-07-18  6:16 dpdklab
2022-07-18  5:37 dpdklab
2022-07-17  5:56 dpdklab
2022-07-17  5:36 dpdklab
2022-07-16  6:07 dpdklab
2022-07-16  5:26 dpdklab
2022-07-15  6:28 dpdklab
2022-07-15  5:39 dpdklab
2022-07-14  6:22 dpdklab
2022-07-14  5:36 dpdklab
2022-07-13  5:56 dpdklab
2022-07-13  5:38 dpdklab
2022-07-12  6:05 dpdklab
2022-07-12  5:31 dpdklab
2022-07-11  5:54 dpdklab
2022-07-11  5:32 dpdklab
2022-07-10  5:30 dpdklab
2022-07-10  5:23 dpdklab
2022-07-09  6:33 dpdklab
2022-07-09  5:31 dpdklab
2022-07-08  5:51 dpdklab
2022-07-08  5:39 dpdklab
2022-07-07  5:20 dpdklab
2022-07-07  5:13 dpdklab
2022-07-06  6:00 dpdklab
2022-07-06  5:32 dpdklab
2022-07-05  6:15 dpdklab
2022-07-05  5:41 dpdklab
2022-07-04  5:28 dpdklab
2022-07-04  5:19 dpdklab
2022-07-03  6:17 dpdklab
2022-07-03  5:26 dpdklab
2022-07-02  6:22 dpdklab
2022-07-02  5:45 dpdklab
2022-07-01  6:20 dpdklab
2022-07-01  5:31 dpdklab
2022-06-30  5:28 dpdklab
2022-06-30  5:28 dpdklab
2022-06-29  6:16 dpdklab
2022-06-29  5:21 dpdklab
2022-06-28  8:16 dpdklab
2022-06-28  7:43 dpdklab
2022-06-27  6:29 dpdklab
2022-06-27  5:42 dpdklab
2022-06-26  6:38 dpdklab
2022-06-26  5:30 dpdklab
2022-06-25  6:33 dpdklab
2022-06-25  5:19 dpdklab
2022-06-24  5:46 dpdklab
2022-06-24  5:21 dpdklab
2022-06-23  6:03 dpdklab
2022-06-23  5:17 dpdklab
2022-06-22  5:20 dpdklab
2022-06-22  5:09 dpdklab
2022-06-21  5:10 dpdklab
2022-06-21  5:10 dpdklab
2022-06-20  5:08 dpdklab
2022-06-20  4:58 dpdklab
2022-06-19  5:12 dpdklab
2022-06-19  5:00 dpdklab
2022-06-18  5:12 dpdklab
2022-06-18  5:07 dpdklab
2022-06-17  5:56 dpdklab
2022-06-17  5:22 dpdklab
2022-06-16  7:03 dpdklab
2022-06-16  5:43 dpdklab
2022-06-15  6:34 dpdklab
2022-06-15  5:22 dpdklab
2022-06-14  6:26 dpdklab
2022-06-14  5:18 dpdklab
2022-06-13  6:23 dpdklab
2022-06-13  5:40 dpdklab
2022-06-12  6:35 dpdklab
2022-06-12  5:35 dpdklab
2022-06-11  7:13 dpdklab
2022-06-11  5:41 dpdklab
2022-06-10  6:57 dpdklab
2022-06-10  5:23 dpdklab
2022-06-09  7:26 dpdklab
2022-06-09  7:16 dpdklab
2022-06-08  6:11 dpdklab
2022-06-08  5:35 dpdklab
2022-06-07  6:37 dpdklab
2022-06-07  5:22 dpdklab
2022-06-06  8:56 dpdklab
2022-06-06  7:23 dpdklab
2022-06-05  6:59 dpdklab
2022-06-05  5:50 dpdklab
2022-06-04  6:38 dpdklab
2022-06-04  5:40 dpdklab
2022-06-03  6:48 dpdklab
2022-06-03  6:38 dpdklab
2022-06-02  7:07 dpdklab
2022-06-02  5:25 dpdklab
2022-06-01  5:39 dpdklab
2022-06-01  5:09 dpdklab
2022-05-31  7:47 dpdklab
2022-05-31  7:41 dpdklab
2022-05-30  6:27 dpdklab
2022-05-30  5:31 dpdklab
2022-05-29  6:58 dpdklab
2022-05-29  5:45 dpdklab
2022-05-28  8:57 dpdklab
2022-05-28  6:59 dpdklab
2022-05-27 22:58 dpdklab
2022-05-27 14:11 dpdklab
2022-05-27  8:25 dpdklab
2022-05-26 10:52 dpdklab
2022-05-26  0:50 dpdklab
2022-05-25  5:52 dpdklab
2022-05-24 10:51 dpdklab
2022-05-24  6:56 dpdklab
2022-05-23  6:01 dpdklab
2022-05-23  5:51 dpdklab
2022-05-22  6:23 dpdklab
2022-05-22  5:35 dpdklab
2022-05-21  6:49 dpdklab
2022-05-21  5:24 dpdklab
2022-05-20 13:24 dpdklab
2022-05-20  8:59 dpdklab
2022-05-19  6:51 dpdklab
2022-05-19  5:36 dpdklab
2022-05-18  8:56 dpdklab
2022-05-18  6:21 dpdklab
2022-05-17  8:15 dpdklab
2022-05-17  7:42 dpdklab
2022-05-16  7:05 dpdklab
2022-05-16  5:24 dpdklab
2022-05-15  6:59 dpdklab
2022-05-15  5:41 dpdklab
2022-05-14  6:49 dpdklab
2022-05-14  5:43 dpdklab
2022-05-13 12:27 dpdklab
2022-05-13  8:19 dpdklab
2022-05-12 21:27 dpdklab
2022-05-12  9:27 dpdklab
2022-05-11 11:51 dpdklab
2022-05-11  7:39 dpdklab
2022-05-10  9:48 dpdklab
2022-05-10  6:37 dpdklab
2022-05-10  1:59 dpdklab
2022-05-09 20:16 dpdklab
2022-05-09 10:19 dpdklab
2022-05-09  0:26 dpdklab
2022-05-08  9:56 dpdklab
2022-05-07  2:54 dpdklab
2022-05-06 19:29 dpdklab
2022-05-05  8:20 dpdklab
2022-05-05  5:35 dpdklab
2022-05-04  7:25 dpdklab
2022-05-04  6:05 dpdklab
2022-05-03  7:58 dpdklab
2022-05-03  5:24 dpdklab
2022-05-02  8:18 dpdklab
2022-05-01  7:58 dpdklab
2022-04-30  8:25 dpdklab
2022-04-29 14:05 dpdklab
2022-04-28 15:46 dpdklab
2022-04-27  5:38 dpdklab
2022-04-26  7:40 dpdklab
2022-04-24  5:35 dpdklab
2022-04-23  5:51 dpdklab
2022-04-23  5:29 dpdklab
2022-04-22  8:58 dpdklab
2022-04-21  7:41 dpdklab
2022-04-20  7:08 dpdklab
2022-04-19  7:07 dpdklab
2022-04-18  6:29 dpdklab
2022-04-17  6:17 dpdklab
2022-04-16  6:34 dpdklab
2022-04-15  8:53 dpdklab
2022-04-12  6:57 dpdklab
2022-04-11  7:44 dpdklab
2022-04-10  6:53 dpdklab
2022-04-09  7:17 dpdklab
2022-04-08  6:48 dpdklab
2022-04-07  6:56 dpdklab
2022-04-06  6:51 dpdklab
2022-04-05  6:48 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=20220509003327.3905B600B3@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).