From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Maayan Kashani <mkashani@nvidia.com>
Subject: |FAILURE| pw140547 [PATCH] app/testpmd: fix parsing for connection t
Date: Sun, 02 Jun 2024 05:04:50 -0700 (PDT) [thread overview]
Message-ID: <665c5fe2.050a0220.4188b.f948SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240602102328.196672-1-mkashani@nvidia.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/140547
_Testing issues_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Sunday, June 02 2024 10:23:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2dbb63594a9a985e2c8639b57f9fcd1468b9de97
140547 --> testing issues
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Ubuntu 24.04 | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
==== 20 line log output for Ubuntu 24.04 (dpdk_unit_test): ====
--- Failed to get log output ---
==== End log output ====
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30071/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-06-02 12:04 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240602102328.196672-1-mkashani@nvidia.com>
2024-06-02 9:56 ` |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection tracking item qemudev
2024-06-02 10:00 ` qemudev
2024-06-02 10:24 ` checkpatch
2024-06-02 11:10 ` |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection t dpdklab
2024-06-02 11:10 ` |FAILURE| " dpdklab
2024-06-02 11:10 ` dpdklab
2024-06-02 11:11 ` |SUCCESS| " dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:12 ` dpdklab
2024-06-02 11:12 ` |FAILURE| " dpdklab
2024-06-02 11:12 ` dpdklab
2024-06-02 11:12 ` dpdklab
2024-06-02 11:12 ` |SUCCESS| " dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` |FAILURE| " dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` |SUCCESS| " dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` |FAILURE| " dpdklab
2024-06-02 11:13 ` |SUCCESS| " dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` |FAILURE| " dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:15 ` |SUCCESS| " dpdklab
2024-06-02 11:15 ` |FAILURE| " dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:15 ` |SUCCESS| " dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:17 ` dpdklab
2024-06-02 11:18 ` dpdklab
2024-06-02 11:18 ` dpdklab
2024-06-02 11:19 ` dpdklab
2024-06-02 11:19 ` dpdklab
2024-06-02 11:20 ` dpdklab
2024-06-02 11:20 ` |FAILURE| " dpdklab
2024-06-02 11:20 ` |SUCCESS| " dpdklab
2024-06-02 11:20 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:22 ` |FAILURE| " dpdklab
2024-06-02 11:22 ` dpdklab
2024-06-02 11:22 ` dpdklab
2024-06-02 11:23 ` |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection tracking item 0-day Robot
2024-06-02 11:26 ` |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection t dpdklab
2024-06-02 11:26 ` dpdklab
2024-06-02 11:27 ` |FAILURE| " dpdklab
2024-06-02 11:29 ` dpdklab
2024-06-02 11:29 ` dpdklab
2024-06-02 11:29 ` dpdklab
2024-06-02 11:30 ` |SUCCESS| " dpdklab
2024-06-02 11:30 ` dpdklab
2024-06-02 11:30 ` dpdklab
2024-06-02 11:30 ` |FAILURE| " dpdklab
2024-06-02 11:30 ` |SUCCESS| " dpdklab
2024-06-02 11:32 ` |FAILURE| " dpdklab
2024-06-02 11:32 ` dpdklab
2024-06-02 11:34 ` |SUCCESS| " dpdklab
2024-06-02 11:35 ` |FAILURE| " dpdklab
2024-06-02 11:36 ` |SUCCESS| " dpdklab
2024-06-02 11:36 ` dpdklab
2024-06-02 11:38 ` |FAILURE| " dpdklab
2024-06-02 11:39 ` |SUCCESS| " dpdklab
2024-06-02 11:39 ` |FAILURE| " dpdklab
2024-06-02 11:41 ` |SUCCESS| " dpdklab
2024-06-02 11:41 ` |FAILURE| " dpdklab
2024-06-02 11:41 ` |SUCCESS| " dpdklab
2024-06-02 11:42 ` |FAILURE| " dpdklab
2024-06-02 11:43 ` dpdklab
2024-06-02 11:43 ` dpdklab
2024-06-02 11:46 ` |SUCCESS| " dpdklab
2024-06-02 11:49 ` dpdklab
2024-06-02 11:50 ` dpdklab
2024-06-02 11:50 ` dpdklab
2024-06-02 11:51 ` |FAILURE| " dpdklab
2024-06-02 11:53 ` dpdklab
2024-06-02 11:53 ` dpdklab
2024-06-02 11:57 ` dpdklab
2024-06-02 12:02 ` dpdklab
2024-06-02 12:04 ` dpdklab [this message]
2024-06-02 12:10 ` dpdklab
2024-06-02 12:11 ` dpdklab
2024-06-02 12:19 ` dpdklab
2024-06-02 12:23 ` 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=665c5fe2.050a0220.4188b.f948SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mkashani@nvidia.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).