From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@xilinx.com>
Subject: |FAILURE| [GIT MASTER] d47a7189e31781bba156550480fa400fa0c4fbe9
Date: Thu, 26 May 2022 20:16:35 +0000 (UTC) [thread overview]
Message-ID: <20220526201635.2A1F96009C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3893 bytes --]
_Testing issues_
Branch: dpdk-next-net
d47a7189e31781bba156550480fa400fa0c4fbe9 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 32 | PASS |
+---------------------+----------------+
| Ubuntu 18.04 | PASS |
+---------------------+----------------+
| Fedora 31 | PASS |
+---------------------+----------------+
| Arch Linux | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 33 | PASS |
+---------------------+----------------+
| Fedora 34 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| RHEL 7 | PASS |
+---------------------+----------------+
| Fedora 34 clang | PASS |
+---------------------+----------------+
| Alpine | FAIL |
+---------------------+----------------+
==== 20 line log output for Alpine (dpdk_unit_test): ====
55/65 DPDK:fast-tests / thash_autotest OK 0.17 s
56/65 DPDK:fast-tests / trace_autotest OK 0.17 s
57/65 DPDK:fast-tests / metrics_autotest OK 0.17 s
58/65 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
59/65 DPDK:fast-tests / telemetry_data_autotest FAIL 4.13 s (killed by signal 11 SIGSEGV)
60/65 DPDK:fast-tests / table_autotest OK 4.52 s
61/65 DPDK:fast-tests / ring_pmd_autotest OK 0.19 s
62/65 DPDK:fast-tests / bitratestats_autotest OK 0.18 s
63/65 DPDK:fast-tests / latencystats_autotest OK 0.17 s
64/65 DPDK:fast-tests / pdump_autotest OK 0.22 s
65/65 DPDK:fast-tests / vdev_autotest OK 0.17 s
Ok: 60
Expected Fail: 0
Fail: 3
Unexpected Pass: 0
Skipped: 2
Timeout: 1
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK@4/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 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
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
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
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-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)
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 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20005/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2022-05-26 20:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220526201635.2A1F96009C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ferruh.yigit@xilinx.com \
--cc=test-report@dpdk.org \
/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).