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] 655f0ed4a75b2ed17a56c3665be32b06323647f9
Date: Mon, 5 Dec 2022 07:59:31 +0000 (UTC) [thread overview]
Message-ID: <20221205075931.46BE960091@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3212 bytes --]
_Testing issues_
Branch: tags/v21.11
655f0ed4a75b2ed17a56c3665be32b06323647f9 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| RHEL 7 | FAIL |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
==== 20 line log output for RHEL 7 (dpdk_unit_test): ====
55/65 DPDK:fast-tests / service_autotest FAIL 2.03 s (exit status 255 or signal 127 SIGinvalid)
56/65 DPDK:fast-tests / thash_autotest OK 0.23 s
57/65 DPDK:fast-tests / trace_autotest OK 0.23 s
58/65 DPDK:fast-tests / metrics_autotest OK 0.33 s
59/65 DPDK:fast-tests / telemetry_json_autotest OK 0.18 s
60/65 DPDK:fast-tests / telemetry_data_autotest OK 0.22 s
61/65 DPDK:fast-tests / ring_pmd_autotest OK 0.47 s
62/65 DPDK:fast-tests / bitratestats_autotest OK 0.22 s
63/65 DPDK:fast-tests / latencystats_autotest OK 0.34 s
64/65 DPDK:fast-tests / pdump_autotest OK 0.33 s
65/65 DPDK:fast-tests / vdev_autotest OK 0.31 s
Ok: 63
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 1
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK@2/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)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/22525/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-12-05 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 7:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-05 7:59 dpdklab
2022-12-05 7:58 dpdklab
2022-12-05 7:56 dpdklab
2022-12-05 7:48 dpdklab
2022-12-03 15:27 dpdklab
2022-12-03 15:27 dpdklab
2022-12-03 15:27 dpdklab
2022-12-03 15:27 dpdklab
2022-12-03 15:26 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=20221205075931.46BE960091@dpdk-ubuntu.dpdklab.iol.unh.edu \
--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).