From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@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] 8010a15523e896ca2f2436432602210cab793f87
Date: Sun, 2 Oct 2022 05:43:43 +0000 (UTC) [thread overview]
Message-ID: <20221002054343.9EEB0601BB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3423 bytes --]
_Testing issues_
Branch: tags/v21.11
8010a15523e896ca2f2436432602210cab793f87 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 31 | PASS |
+---------------------+----------------+
| RHEL8 | FAIL |
+---------------------+----------------+
| RHEL 7 | PASS |
+---------------------+----------------+
| Fedora 33 | FAIL |
+---------------------+----------------+
| Fedora 32 | PASS |
+---------------------+----------------+
| Ubuntu 18.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 34 clang | PASS |
+---------------------+----------------+
| Fedora 34 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
==== 20 line log output for Fedora 33 (dpdk_unit_test): ====
55/65 DPDK:fast-tests / service_autotest FAIL 2.87 s (exit status 255 or signal 127 SIGinvalid)
56/65 DPDK:fast-tests / thash_autotest OK 0.34 s
57/65 DPDK:fast-tests / trace_autotest OK 0.34 s
58/65 DPDK:fast-tests / metrics_autotest OK 0.39 s
59/65 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
60/65 DPDK:fast-tests / telemetry_data_autotest OK 0.35 s
61/65 DPDK:fast-tests / ring_pmd_autotest OK 0.40 s
62/65 DPDK:fast-tests / bitratestats_autotest OK 0.22 s
63/65 DPDK:fast-tests / latencystats_autotest OK 0.48 s
64/65 DPDK:fast-tests / pdump_autotest OK 0.63 s
65/65 DPDK:fast-tests / vdev_autotest OK 0.28 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@3/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)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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)
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/21579/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-10-02 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 5:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-25 5:59 dpdklab
2022-10-24 5:42 dpdklab
2022-10-07 6:27 dpdklab
2022-09-26 6:16 dpdklab
2022-09-23 5:59 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=20221002054343.9EEB0601BB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--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).