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] 6be826afff5fdc4ceb3f6ae68d8a0b6e50aaf0a0
Date: Thu, 04 Apr 2024 03:22:07 -0700 (PDT) [thread overview]
Message-ID: <660e7f4f.050a0220.66e21.7259SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing issues_
Branch: 21.11-staging
6be826afff5fdc4ceb3f6ae68d8a0b6e50aaf0a0 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 6
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
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 0.52 s (exit status 255 or signal 127 SIGinvalid)
2/2 DPDK:driver-tests / cryptodev_openssl_asym_autotest OK 0.17 s
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.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 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
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28717/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-04-04 10:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 10:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-04 17:25 dpdklab
2024-04-04 17:24 dpdklab
2024-04-04 17:23 dpdklab
2024-04-04 16:58 dpdklab
2024-04-04 10:49 dpdklab
2024-04-04 10:45 dpdklab
2024-04-04 10:43 dpdklab
2024-04-04 10:37 dpdklab
2024-04-04 10:34 dpdklab
2024-04-04 10:34 dpdklab
2024-04-04 10:33 dpdklab
2024-04-04 10:31 dpdklab
2024-04-04 10:27 dpdklab
2024-04-04 10:26 dpdklab
2024-04-04 10:17 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=660e7f4f.050a0220.66e21.7259SMTPIN_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).