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, Brian Dooley <brian.dooley@intel.com>
Subject: |WARNING| pw138212-138216 [PATCH] [v6,5/5] crypto/ipsec_mb: unify so
Date: Tue, 12 Mar 2024 07:43:32 -0700 (PDT)	[thread overview]
Message-ID: <65f06a14.d40a0220.329b2.506aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240312135020.2969533-5-brian.dooley@intel.com>

Test-Label: iol-unit-arm64-testing
Test-Status: WARNING
http://dpdk.org/patch/138216

_Testing issues_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Tuesday, March 12 2024 13:50:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138212-138216 --> testing fail

Test environment and result as below:

+--------------------------+------------------------------+---------------------------+----------------+--------------+
|       Environment        | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test | lpm_autotest |
+==========================+==============================+===========================+================+==============+
| Debian 12 (arm)          | FAIL                         | FAIL                      | PASS           | SKIPPED      |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 37 (ARM)          | SKIPPED                      | SKIPPED                   | PASS           | SKIPPED      |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)    | SKIPPED                      | SKIPPED                   | PASS           | SKIPPED      |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | SKIPPED                      | SKIPPED                   | PASS           | SKIPPED      |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Ubuntu 20.04 (ARM)       | SKIPPED                      | SKIPPED                   | PASS           | SKIPPED      |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 38 (ARM)          | SKIPPED                      | SKIPPED                   | PASS           | SKIPPED      |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE     | SKIPPED                      | SKIPPED                   | SKIPPED        | PASS         |
+--------------------------+------------------------------+---------------------------+----------------+--------------+

==== 20 line log output for Debian 12 (arm) (cryptodev_sw_zuc_autotest): ====
[2440/3177] Generating drivers/rte_crypto_ipsec_mb.pmd.c with a custom command
[2441/3177] Compiling C object drivers/librte_crypto_ipsec_mb.a.p/meson-generated_.._rte_crypto_ipsec_mb.pmd.c.o
[2442/3177] Linking target drivers/librte_regex_cn9k.so.24.1
[2443/3177] Compiling C object drivers/libtmp_rte_vdpa_ifc.a.p/vdpa_ifc_ifcvf_vdpa.c.o
[2444/3177] Linking static target drivers/librte_crypto_ipsec_mb.a
[2445/3177] Compiling C object drivers/librte_crypto_ipsec_mb.so.24.1.p/meson-generated_.._rte_crypto_ipsec_mb.pmd.c.o
[2446/3177] Compiling C object drivers/libtmp_rte_vdpa_ifc.a.p/vdpa_ifc_base_ifcvf.c.o
[2447/3177] Linking static target drivers/libtmp_rte_vdpa_ifc.a
[2448/3177] Compiling C object drivers/libtmp_rte_vdpa_mlx5.a.p/vdpa_mlx5_mlx5_vdpa.c.o
[2449/3177] Compiling C object drivers/libtmp_rte_vdpa_mlx5.a.p/vdpa_mlx5_mlx5_vdpa_mem.c.o
[2450/3177] Linking target drivers/librte_crypto_ipsec_mb.so.24.1
FAILED: drivers/librte_crypto_ipsec_mb.so.24.1
cc  -o drivers/librte_crypto_ipsec_mb.so.24.1 drivers/librte_crypto_ipsec_mb.so.24.1.p/meson-generated_.._rte_crypto_ipsec_mb.pmd.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_private.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_ipsec_mb_ops.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_gcm.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_chacha_poly.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_kasumi.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_snow3g.c.o drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_zuc.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,librte_crypto_ipsec_mb.so.24 -Wl,--no-as-needed -Wl,--undefined-version -pthread -lm -ldl -lnuma -march=armv8-a+crc+crypto '-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/' -Wl,-rpath-link,/home-local/jenkins-local/
 jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/lib -Wl,-rpath-link,/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/drivers lib/librte_cryptodev.so.24.1 lib/librte_eal.so.24.1 lib/librte_kvargs.so.24.1 lib/librte_log.so.24.1 lib/librte_telemetry.so.24.1 lib/librte_mbuf.so.24.1 lib/librte_mempool.so.24.1 lib/librte_ring.so.24.1 lib/librte_rcu.so.24.1 drivers/librte_bus_vdev.so.24.1 lib/librte_net.so.24.1 lib/librte_security.so.24.1 -Wl,--version-script=/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/drivers/version.map -lIPSec_MB -Wl,--end-group
/usr/bin/ld: drivers/libtmp_rte_crypto_ipsec_mb.a.p/crypto_ipsec_mb_pmd_aesni_mb.c.o: in function `aesni_mb_set_session_auth_parameters.constprop.0':
pmd_aesni_mb.c:(.text+0xd34): undefined reference to `imb_hmac_ipad_opad'
collect2: error: ld returned 1 exit status
[2451/3177] Compiling C object drivers/libtmp_rte_vdpa_mlx5.a.p/vdpa_mlx5_mlx5_vdpa_event.c.o
[2452/3177] Generating drivers/rte_ml_cnxk.pmd.c with a custom command
[2453/3177] Generating drivers/rte_vdpa_ifc.pmd.c with a custom command
ninja: build stopped: subcommand failed.
==== End log output ====

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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

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

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

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-12 14:43 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312135020.2969533-5-brian.dooley@intel.com>
2024-03-12 13:28 ` |SUCCESS| pw138212-138216 [PATCH v6 5/5] crypto/ipsec_mb: unify some IPsec MB PMDs qemudev
2024-03-12 13:33 ` qemudev
2024-03-12 13:52 ` |SUCCESS| pw138216 " checkpatch
2024-03-12 14:24 ` |SUCCESS| pw138212-138216 [PATCH] [v6,5/5] crypto/ipsec_mb: unify so dpdklab
2024-03-12 14:24 ` dpdklab
2024-03-12 14:24 ` dpdklab
2024-03-12 14:24 ` dpdklab
2024-03-12 14:24 ` dpdklab
2024-03-12 14:25 ` dpdklab
2024-03-12 14:25 ` dpdklab
2024-03-12 14:25 ` dpdklab
2024-03-12 14:25 ` dpdklab
2024-03-12 14:26 ` dpdklab
2024-03-12 14:26 ` dpdklab
2024-03-12 14:26 ` dpdklab
2024-03-12 14:26 ` dpdklab
2024-03-12 14:26 ` dpdklab
2024-03-12 14:27 ` dpdklab
2024-03-12 14:27 ` dpdklab
2024-03-12 14:27 ` dpdklab
2024-03-12 14:27 ` dpdklab
2024-03-12 14:27 ` dpdklab
2024-03-12 14:28 ` dpdklab
2024-03-12 14:28 ` dpdklab
2024-03-12 14:28 ` dpdklab
2024-03-12 14:29 ` dpdklab
2024-03-12 14:29 ` dpdklab
2024-03-12 14:29 ` dpdklab
2024-03-12 14:29 ` dpdklab
2024-03-12 14:30 ` dpdklab
2024-03-12 14:30 ` dpdklab
2024-03-12 14:30 ` dpdklab
2024-03-12 14:30 ` dpdklab
2024-03-12 14:30 ` dpdklab
2024-03-12 14:31 ` dpdklab
2024-03-12 14:31 ` |WARNING| " dpdklab
2024-03-12 14:31 ` |SUCCESS| " dpdklab
2024-03-12 14:31 ` dpdklab
2024-03-12 14:31 ` dpdklab
2024-03-12 14:31 ` |WARNING| " dpdklab
2024-03-12 14:32 ` dpdklab
2024-03-12 14:32 ` |SUCCESS| " dpdklab
2024-03-12 14:32 ` dpdklab
2024-03-12 14:32 ` dpdklab
2024-03-12 14:33 ` dpdklab
2024-03-12 14:33 ` |WARNING| " dpdklab
2024-03-12 14:33 ` |SUCCESS| " dpdklab
2024-03-12 14:33 ` |WARNING| " dpdklab
2024-03-12 14:34 ` |SUCCESS| " dpdklab
2024-03-12 14:34 ` dpdklab
2024-03-12 14:34 ` dpdklab
2024-03-12 14:34 ` |WARNING| " dpdklab
2024-03-12 14:35 ` |SUCCESS| " dpdklab
2024-03-12 14:36 ` dpdklab
2024-03-12 14:36 ` dpdklab
2024-03-12 14:37 ` dpdklab
2024-03-12 14:37 ` dpdklab
2024-03-12 14:41 ` dpdklab
2024-03-12 14:42 ` |SUCCESS| pw138216 [PATCH v6 5/5] crypto/ipsec_mb: unify some IPsec MB PMDs 0-day Robot
2024-03-12 14:43 ` dpdklab [this message]
2024-03-12 14:45 ` |SUCCESS| pw138212-138216 [PATCH] [v6,5/5] crypto/ipsec_mb: unify so dpdklab
2024-03-12 14:46 ` dpdklab
2024-03-12 14:46 ` dpdklab
2024-03-12 14:49 ` dpdklab
2024-03-12 14:50 ` dpdklab
2024-03-12 14:57 ` |WARNING| " dpdklab
2024-03-12 15:55 ` |SUCCESS| " dpdklab
2024-03-15 19:07 ` |WARNING| " dpdklab
2024-03-15 19:14 ` dpdklab
2024-03-15 19:18 ` |SUCCESS| " dpdklab
2024-03-15 19:31 ` dpdklab
2024-03-15 19:39 ` dpdklab
2024-03-15 19:41 ` dpdklab
2024-03-15 19:42 ` dpdklab
2024-03-15 19:42 ` dpdklab
2024-03-15 19:45 ` dpdklab
2024-03-15 19:45 ` dpdklab
2024-03-15 19:46 ` dpdklab
2024-03-15 19:48 ` dpdklab
2024-03-15 19:50 ` dpdklab
2024-03-15 19:51 ` dpdklab
2024-03-15 19:51 ` dpdklab
2024-03-15 19:53 ` dpdklab
2024-03-15 19:57 ` dpdklab
2024-03-15 20:15 ` dpdklab
2024-03-15 20:21 ` dpdklab
2024-03-15 20:24 ` dpdklab
2024-03-15 20:28 ` dpdklab
2024-03-15 20:29 ` dpdklab
2024-03-15 20:35 ` dpdklab
2024-03-15 21:18 ` dpdklab
2024-03-15 23:47 ` dpdklab
2024-03-16  0:23 ` 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=65f06a14.d40a0220.329b2.506aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=brian.dooley@intel.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).