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] a0bb9efc615dd2753788826b1a6ad86024dd298e
Date: Sun, 28 Jul 2024 00:02:24 -0700 (PDT)	[thread overview]
Message-ID: <66a5ed00.050a0220.7f5e3.eb73SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v22.11

a0bb9efc615dd2753788826b1a6ad86024dd298e --> testing issues

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 40           | PEND           |
+---------------------+----------------+
| RHEL8               | PEND           |
+---------------------+----------------+
| RHEL 7              | WARN           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL9               | PEND           |
+---------------------+----------------+
| Ubuntu 20.04        | PEND           |
+---------------------+----------------+
| Ubuntu 22.04        | PEND           |
+---------------------+----------------+
| Ubuntu 24.04        | PEND           |
+---------------------+----------------+

==== 20 line log output for RHEL 7 (dpdk_unit_test): ====
../drivers/crypto/openssl/rte_openssl_pmd.c:897:2: error: 'for' loop initial declarations are only allowed in C99 mode
for (uint16_t i = 0; i < sess->ctx_copies_len; i++) {
^
../drivers/crypto/openssl/rte_openssl_pmd.c:897:2: note: use option -std=c99 or -std=gnu99 to compile your code
../drivers/crypto/openssl/rte_openssl_pmd.c: In function 'get_local_auth_ctx':
../drivers/crypto/openssl/rte_openssl_pmd.c:1667:3: error: implicit declaration of function 'EVP_MD_CTX_new' [-Werror=implicit-function-declaration]
*lctx = EVP_MD_CTX_new();
^
../drivers/crypto/openssl/rte_openssl_pmd.c:1667:3: error: nested extern declaration of 'EVP_MD_CTX_new' [-Werror=nested-externs]
../drivers/crypto/openssl/rte_openssl_pmd.c:1667:9: error: assignment makes pointer from integer without a cast [-Werror]
*lctx = EVP_MD_CTX_new();
^
../drivers/crypto/openssl/rte_openssl_pmd.c: At top level:
../drivers/crypto/openssl/rte_openssl_pmd.c:34:13: error: 'HMAC_CTX_free' defined but not used [-Werror=unused-function]
static void HMAC_CTX_free(HMAC_CTX *ctx)
^
cc1: all warnings being treated as errors
[2474/3479] Compiling C object 'drivers/a715181@@tmp_rte_crypto_scheduler@sta/crypto_scheduler_rte_cryptodev_scheduler.c.o'.
[2475/3479] Compiling C object 'drivers/a715181@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

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

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

RHEL 7
	Kernel: 5.4.0-167-generic
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-28 10:06 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28  7:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-29  6:39 dpdklab
2024-07-29  6:36 dpdklab
2024-07-29  6:36 dpdklab
2024-07-29  6:35 dpdklab
2024-07-29  6:33 dpdklab
2024-07-29  6:31 dpdklab
2024-07-29  6:29 dpdklab
2024-07-29  6:22 dpdklab
2024-07-29  6:18 dpdklab
2024-07-29  6:12 dpdklab
2024-07-29  6:11 dpdklab
2024-07-29  6:10 dpdklab
2024-07-29  6:08 dpdklab
2024-07-29  5:46 dpdklab
2024-07-29  5:45 dpdklab
2024-07-29  5:44 dpdklab
2024-07-29  5:43 dpdklab
2024-07-28  7:18 dpdklab
2024-07-28  7:15 dpdklab
2024-07-28  7:14 dpdklab
2024-07-28  7:11 dpdklab
2024-07-28  7:05 dpdklab
2024-07-28  7:02 dpdklab
2024-07-28  7:00 dpdklab
2024-07-28  6:54 dpdklab
2024-07-28  6:51 dpdklab
2024-07-28  6:48 dpdklab
2024-07-28  6:41 dpdklab
2024-07-28  6:34 dpdklab
2024-07-28  6:32 dpdklab
2024-07-28  6:32 dpdklab
2024-07-28  6:29 dpdklab
2024-07-27  8:11 dpdklab
2024-07-27  8:09 dpdklab
2024-07-27  8:04 dpdklab
2024-07-27  7:57 dpdklab
2024-07-27  7:55 dpdklab
2024-07-27  7:54 dpdklab
2024-07-27  7:52 dpdklab
2024-07-27  7:51 dpdklab
2024-07-27  7:46 dpdklab
2024-07-27  7:44 dpdklab
2024-07-27  7:39 dpdklab
2024-07-27  7:35 dpdklab
2024-07-27  7:32 dpdklab
2024-07-27  7:23 dpdklab
2024-07-26 12:47 dpdklab
2024-07-26 11:39 dpdklab
2024-07-26 11:21 dpdklab
2024-07-26 11:18 dpdklab
2024-07-26 11:03 dpdklab
2024-07-26 11:01 dpdklab
2024-07-26 10:59 dpdklab
2024-07-26 10:58 dpdklab
2024-07-26 10:52 dpdklab
2024-07-26 10:45 dpdklab
2024-07-26 10:42 dpdklab
2024-07-26 10:40 dpdklab
2024-07-26 10:40 dpdklab
2024-07-26 10:32 dpdklab
2024-07-26 10:30 dpdklab
2024-07-26 10:29 dpdklab
2024-07-26 10:29 dpdklab
2024-07-26 10:29 dpdklab
2024-07-26 10:27 dpdklab
2024-07-26 10:25 dpdklab
2024-07-26 10:22 dpdklab
2024-07-26 10:22 dpdklab
2024-07-26 10:13 dpdklab
2024-07-26 10:09 dpdklab
2024-07-26 10:09 dpdklab
2024-07-26 10:04 dpdklab
2024-07-26  9:52 dpdklab
2024-07-26  9:49 dpdklab
2024-07-26  8:20 dpdklab
2024-07-25 12:52 dpdklab
2024-07-25 12:47 dpdklab
2024-07-25 12:42 dpdklab
2024-07-25 12:42 dpdklab
2024-07-25 12:42 dpdklab
2024-07-25 12:40 dpdklab
2024-07-25 12:39 dpdklab
2024-07-25 12:37 dpdklab
2024-07-25 12:36 dpdklab
2024-07-25 12:29 dpdklab
2024-07-25 12:28 dpdklab
2024-07-25 12:25 dpdklab
2024-07-25 12:22 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=66a5ed00.050a0220.7f5e3.eb73SMTPIN_ADDED_MISSING@mx.google.com \
    --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).