From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: |FAILURE| pw124882-124885 [PATCH] [4/4] mempool: use lcore API to check if lcore ID is valid
Date: Sun, 12 Mar 2023 12:48:00 +0000 (UTC) [thread overview]
Message-ID: <20230312124800.0F8C76011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/124885
_Testing issues_
Submitter: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Date: Thursday, March 09 2023 04:57:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b15d75b2872efce397d827dac78692a919358302
124882-124885 --> testing fail
Test environment and result as below:
+----------------------------------------+----------------+--------------------+----------------------+
| Environment | dpdk_unit_test | dpdk_meson_compile | dpdk_mingw64_compile |
+========================================+================+====================+======================+
| Ubuntu 20.04 ARM GCC Native | FAIL | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM Clang Native | FAIL | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS | PASS |
+----------------------------------------+----------------+--------------------+----------------------+
| Debian Buster | FAIL | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 22.04 | FAIL | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 | FAIL | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| openSUSE Leap 15 | FAIL | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| FreeBSD 13 | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 8 | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 9 | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Debian Bullseye | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| RHEL 7 | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| RHEL8 | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS | SKIPPED |
+----------------------------------------+----------------+--------------------+----------------------+
==== 20 line log output for openSUSE Leap 15 (dpdk_unit_test): ====
93/103 DPDK:fast-tests / telemetry_json_autotest OK 0.19 s
94/103 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
95/103 DPDK:fast-tests / table_autotest OK 8.25 s
96/103 DPDK:fast-tests / ring_pmd_autotest OK 0.18 s
97/103 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.63 s
98/103 DPDK:fast-tests / bitratestats_autotest OK 0.19 s
99/103 DPDK:fast-tests / latencystats_autotest OK 0.23 s
100/103 DPDK:fast-tests / pdump_autotest FAIL 0.39 s (killed by signal 11 SIGSEGV)
101/103 DPDK:fast-tests / vdev_autotest OK 0.23 s
102/103 DPDK:fast-tests / compressdev_autotest SKIP 0.22 s
103/103 DPDK:fast-tests / telemetry_all SKIP 0.02 s
Ok: 92
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 10
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 ====
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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)
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 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25654/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-12 12:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 12:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-12 14:36 dpdklab
2023-03-12 14:07 dpdklab
2023-03-12 14:05 dpdklab
2023-03-12 14:03 dpdklab
2023-03-12 13:56 dpdklab
2023-03-12 13:52 dpdklab
2023-03-12 13:51 dpdklab
2023-03-12 13:50 dpdklab
2023-03-12 13:50 dpdklab
2023-03-12 13:49 dpdklab
2023-03-12 13:46 dpdklab
2023-03-12 13:39 dpdklab
2023-03-12 13:36 dpdklab
2023-03-12 13:31 dpdklab
2023-03-12 13:00 dpdklab
2023-03-12 12:56 dpdklab
2023-03-12 12:54 dpdklab
2023-03-12 12:52 dpdklab
2023-03-12 12:51 dpdklab
2023-03-12 12:48 dpdklab
2023-03-12 12:42 dpdklab
2023-03-12 12:37 dpdklab
2023-03-12 12:36 dpdklab
2023-03-12 12:31 dpdklab
2023-03-11 4:40 dpdklab
2023-03-11 4:16 dpdklab
2023-03-11 4:15 dpdklab
[not found] <20230309045738.1261000-5-honnappa.nagarahalli@arm.com>
2023-03-09 4:51 ` |FAILURE| pw124882-124885 [PATCH 4/4] " qemudev
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=20230312124800.0F8C76011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=honnappa.nagarahalli@arm.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).