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| pw148425-148429 [PATCH] [RFC,5/5] test: remove unneeded me
Date: Wed, 13 Nov 2024 18:04:21 -0800 (PST)	[thread overview]
Message-ID: <67355aa5.050a0220.1c147a.0750SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241113185720.28706-6-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/148429

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, November 13 2024 18:56:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c5df7a373ad07413d9652479272cd16adf989b06

148425-148429 --> testing issues

Upstream job id: Generic-DPDK-Compile-Meson#333258

Test environment and result as below:

+-------------------+--------------------+------------------+-------------------+
|    Environment    | dpdk_meson_compile | dpdk_compile_ovs | dpdk_compile_spdk |
+===================+====================+==================+===================+
| CentOS Stream 9   | FAIL               | WARN             | WARN              |
+-------------------+--------------------+------------------+-------------------+
| Fedora 39         | FAIL               | WARN             | WARN              |
+-------------------+--------------------+------------------+-------------------+
| Debian 12         | FAIL               | WARN             | WARN              |
+-------------------+--------------------+------------------+-------------------+
| Fedora 39 (Clang) | FAIL               | WARN             | WARN              |
+-------------------+--------------------+------------------+-------------------+
| RHEL8             | FAIL               | WARN             | SKIPPED           |
+-------------------+--------------------+------------------+-------------------+
| openSUSE Leap 15  | FAIL               | WARN             | SKIPPED           |
+-------------------+--------------------+------------------+-------------------+
| Fedora 40         | FAIL               | WARN             | WARN              |
+-------------------+--------------------+------------------+-------------------+
| Fedora 40 (Clang) | FAIL               | WARN             | WARN              |
+-------------------+--------------------+------------------+-------------------+
| Ubuntu 20.04      | FAIL               | WARN             | SKIPPED           |
+-------------------+--------------------+------------------+-------------------+
| Alpine            | FAIL               | WARN             | SKIPPED           |
+-------------------+--------------------+------------------+-------------------+
| RHEL9             | FAIL               | WARN             | SKIPPED           |
+-------------------+--------------------+------------------+-------------------+
| FreeBSD 13.4      | FAIL               | SKIPPED          | SKIPPED           |
+-------------------+--------------------+------------------+-------------------+
| FreeBSD 14.1      | FAIL               | SKIPPED          | SKIPPED           |
+-------------------+--------------------+------------------+-------------------+

==== 20 line log output for FreeBSD 14.1 (dpdk_meson_compile): ====
|                 ~~~~~~~~                          ^
/usr/include/string.h:169:9: note: 'memset_s' declared here
169 | errno_t memset_s(void *, rsize_t, int, rsize_t);
|         ^        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/qat/qat_asym.c:1475:3: error: too few arguments to function call, expected 4, have 3
1475 |                 PARAM_CLR(rsa->qt.qInv);
|                 ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/qat/qat_asym.c:106:37: note: expanded from macro 'PARAM_CLR'
106 |                 memset_s(what.data, 0, what.length); \
|                 ~~~~~~~~                          ^
/usr/include/string.h:169:9: note: 'memset_s' declared here
169 | errno_t memset_s(void *, rsize_t, int, rsize_t);
|         ^        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11 errors generated.
[603/1864] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_crypto.c.o
[604/1864] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o
[605/1864] Generating drivers/rte_common_idpf.sym_chk with a custom command (wrapped by meson to capture output)
[606/1864] Generating lib/pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[607/1864] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_dev_qat_sym_pmd_gen1.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

openSUSE Leap 15
	Kernel: Depends on container host
	Compiler: gcc (SUSE Linux) 7.5.0

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Alpine
	Kernel: Depends on container host
	Compiler: gcc (Alpine 13.2.1_git20240309) 13.2.1 20240309

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-11-14  2:04 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241113185720.28706-6-stephen@networkplumber.org>
2024-11-13 18:28 ` |FAILURE| pw148425-148429 [RFC 5/5] test: remove unneeded memset qemudev
2024-11-13 18:59 ` |SUCCESS| pw148429 " checkpatch
2024-11-13 19:45 ` |FAILURE| " 0-day Robot
2024-11-13 21:00 ` |SUCCESS| pw148425-148429 [PATCH] [RFC,5/5] test: remove unneeded me dpdklab
2024-11-13 21:57 ` dpdklab
2024-11-13 22:58 ` dpdklab
2024-11-13 23:28 ` dpdklab
2024-11-13 23:59 ` |FAILURE| " dpdklab
2024-11-14  0:12 ` |WARNING| " dpdklab
2024-11-14  0:12 ` dpdklab
2024-11-14  0:31 ` |PENDING| " dpdklab
2024-11-14  0:49 ` |FAILURE| " dpdklab
2024-11-14  0:50 ` dpdklab
2024-11-14  0:52 ` dpdklab
2024-11-14  0:53 ` dpdklab
2024-11-14  0:54 ` |PENDING| " dpdklab
2024-11-14  0:54 ` |FAILURE| " dpdklab
2024-11-14  0:56 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  1:00 ` dpdklab
2024-11-14  1:00 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:02 ` dpdklab
2024-11-14  1:02 ` |WARNING| " dpdklab
2024-11-14  1:03 ` dpdklab
2024-11-14  1:18 ` dpdklab
2024-11-14  1:18 ` dpdklab
2024-11-14  1:39 ` dpdklab
2024-11-14  2:02 ` |FAILURE| " dpdklab
2024-11-14  2:03 ` dpdklab
2024-11-14  2:04 ` dpdklab [this message]
2024-11-14  2:06 ` dpdklab
2024-11-14  2:21 ` |PENDING| " dpdklab
2024-11-14  2:22 ` |WARNING| " dpdklab
2024-11-14  2:23 ` dpdklab
2024-11-14  2:59 ` |FAILURE| " dpdklab
2024-11-14  3:07 ` dpdklab
2024-11-14  3:23 ` dpdklab
2024-11-14  3:23 ` dpdklab
2024-11-14  3:44 ` |WARNING| " dpdklab
2024-11-14  3:45 ` dpdklab
2024-11-14  4:24 ` |FAILURE| " dpdklab
2024-11-14  4:28 ` 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=67355aa5.050a0220.1c147a.0750SMTPIN_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).