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] 1e1f6d551be99b66b7d2e0a937a6e8a7aa8f1f1d
Date: Fri, 08 Mar 2024 06:57:26 -0800 (PST) [thread overview]
Message-ID: <65eb2756.050a0220.b5cf2.cf54SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: 21.11-staging
1e1f6d551be99b66b7d2e0a937a6e8a7aa8f1f1d --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 (arm) | FAIL |
+---------------------+----------------+
==== 20 line log output for Debian 12 (arm) (dpdk_unit_test): ====
Installing symlink pointing to librte_baseband_null.so.22 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-22.0/librte_baseband_null.so
Installing symlink pointing to librte_baseband_turbo_sw.so.22.0 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-22.0/librte_baseband_turbo_sw.so.22
Installing symlink pointing to librte_baseband_turbo_sw.so.22 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-22.0/librte_baseband_turbo_sw.so
Running custom install script '/bin/sh /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/config/../buildtools/symlink-drivers-solibs.sh lib/x86_64-linux-gnu dpdk/pmds-22.0'
ninja: no work to do.
ninja: Entering directory `/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
1/2 DPDK:driver-tests / cryptodev_openssl_autotest FAIL 1.96s (exit status 255 or signal 127 SIGinvalid)
>>> DPDK_TEST=cryptodev_openssl_autotest MALLOC_PERTURB_=122 /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test --vdev crypto_openssl
2/2 DPDK:driver-tests / cryptodev_openssl_asym_autotest OK 0.40s
Ok: 1
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 0
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28395/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-03-08 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 14:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 7:20 dpdklab
2024-03-08 15:46 dpdklab
2024-03-08 15:45 dpdklab
2024-03-08 15:40 dpdklab
2024-03-08 15:37 dpdklab
2024-03-08 15:37 dpdklab
2024-03-08 15:35 dpdklab
2024-03-08 15:30 dpdklab
2024-03-08 15:30 dpdklab
2024-03-08 15:14 dpdklab
2024-03-08 15:06 dpdklab
2024-03-08 14:51 dpdklab
2024-03-08 14:48 dpdklab
2024-03-08 14:46 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=65eb2756.050a0220.b5cf2.cf54SMTPIN_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).