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] c5dc4f6eb5718da16cad951784242edfa26eb578
Date: Tue, 16 Aug 2022 05:44:17 +0000 (UTC) [thread overview]
Message-ID: <20220816054417.B982F6043F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3439 bytes --]
_Testing issues_
Branch: tags/v20.11
c5dc4f6eb5718da16cad951784242edfa26eb578 --> testing fail
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Fedora 34 | FAIL |
+------------------+----------------+
| Fedora 32 | FAIL |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Ubuntu 18.04 | FAIL |
+------------------+----------------+
| Fedora 34 clang | FAIL |
+------------------+----------------+
| Fedora 31 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | FAIL |
+------------------+----------------+
| RHEL 7 | FAIL |
+------------------+----------------+
| Fedora 33 | FAIL |
+------------------+----------------+
==== 20 line log output for Fedora 33 (dpdk_unit_test): ====
21/94 DPDK:fast-tests / eal_flags_file_prefix_autotest OK 4.03 s
22/94 DPDK:fast-tests / eal_flags_misc_autotest OK 1.53 s
23/94 DPDK:fast-tests / eal_fs_autotest OK 0.27 s
24/94 DPDK:fast-tests / errno_autotest OK 0.27 s
25/94 DPDK:fast-tests / ethdev_link_status OK 0.27 s
26/94 DPDK:fast-tests / event_ring_autotest OK 0.27 s
27/94 DPDK:fast-tests / fib_autotest OK 1.12 s
28/94 DPDK:fast-tests / fib6_autotest OK 1.07 s
29/94 DPDK:fast-tests / func_reentrancy_autotest OK 6.25 s
30/94 DPDK:fast-tests / flow_classify_autotest OK 0.27 s
31/94 DPDK:fast-tests / hash_autotest OK 0.62 s
32/94 DPDK:fast-tests / interrupt_autotest OK 1.42 s
33/94 DPDK:fast-tests / ipfrag_autotest OK 0.27 s
34/94 DPDK:fast-tests / lcores_autotest OK 1.92 s
35/94 DPDK:fast-tests / logs_autotest OK 0.22 s
36/94 DPDK:fast-tests / lpm_autotest OK 5.53 s
37/94 DPDK:fast-tests / lpm6_autotest OK 7.84 s
38/94 DPDK:fast-tests / malloc_autotest OK 3.08 s
39/94 DPDK:fast-tests / mbuf_autotest OK 14.77 s
40/94 DPDK:fast-tests / mcslock_autotest TIMEOUT 602.06 s
==== End log output ====
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/21045/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-08-16 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 5:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-17 5:32 dpdklab
2022-08-15 11:30 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=20220816054417.B982F6043F@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).