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| pw140825-140835 [PATCH] [v5,11/11] net/mlx5: initial desig
Date: Thu, 06 Jun 2024 10:26:23 -0700 (PDT) [thread overview]
Message-ID: <6661f13f.050a0220.4c92a.628cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240606123256.177947-11-mkashani@nvidia.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/140835
_Testing issues_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Thursday, June 06 2024 12:32:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2bf363ff7e924a1fb6054eee693fde66097273f7
140825-140835 --> testing issues
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
| Debian 12 | FAIL |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 39 | FAIL |
+---------------------+----------------+
| Fedora 38 | FAIL |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
| RHEL8 | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | FAIL |
+---------------------+----------------+
| Ubuntu 22.04 | FAIL |
+---------------------+----------------+
| Ubuntu 24.04 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
==== 20 line log output for CentOS Stream 8 (dpdk_unit_test): ====
--- Failed to get log output ---
==== End log output ====
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30133/
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-06 17:26 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240606123256.177947-11-mkashani@nvidia.com>
2024-06-06 12:37 ` |SUCCESS| pw140835 [PATCH v5 11/11] net/mlx5: initial design changes checkpatch
2024-06-06 17:02 ` |WARNING| pw140825-140835 [PATCH] [v5,11/11] net/mlx5: initial desig dpdklab
2024-06-06 17:20 ` dpdklab
2024-06-06 17:21 ` |FAILURE| " dpdklab
2024-06-06 17:21 ` dpdklab
2024-06-06 17:22 ` |WARNING| " dpdklab
2024-06-06 17:22 ` dpdklab
2024-06-06 17:22 ` |FAILURE| " dpdklab
2024-06-06 17:22 ` |WARNING| " dpdklab
2024-06-06 17:23 ` |FAILURE| " dpdklab
2024-06-06 17:23 ` dpdklab
2024-06-06 17:24 ` dpdklab
2024-06-06 17:24 ` dpdklab
2024-06-06 17:24 ` dpdklab
2024-06-06 17:25 ` dpdklab
2024-06-06 17:25 ` dpdklab
2024-06-06 17:25 ` dpdklab
2024-06-06 17:25 ` dpdklab
2024-06-06 17:25 ` dpdklab
2024-06-06 17:26 ` dpdklab
2024-06-06 17:26 ` |WARNING| " dpdklab
2024-06-06 17:26 ` dpdklab [this message]
2024-06-06 17:26 ` dpdklab
2024-06-06 17:26 ` |FAILURE| " dpdklab
2024-06-06 17:27 ` dpdklab
2024-06-06 17:27 ` dpdklab
2024-06-06 17:27 ` dpdklab
2024-06-06 17:27 ` dpdklab
2024-06-06 17:27 ` |WARNING| " dpdklab
2024-06-06 17:27 ` |FAILURE| " dpdklab
2024-06-06 17:28 ` dpdklab
2024-06-06 17:28 ` dpdklab
2024-06-06 17:28 ` dpdklab
2024-06-06 17:28 ` dpdklab
2024-06-06 17:28 ` dpdklab
2024-06-06 17:28 ` dpdklab
2024-06-06 17:29 ` dpdklab
2024-06-06 17:29 ` dpdklab
2024-06-06 17:31 ` dpdklab
2024-06-06 17:31 ` dpdklab
2024-06-06 17:32 ` dpdklab
2024-06-06 17:32 ` dpdklab
2024-06-06 17:32 ` |WARNING| " dpdklab
2024-06-06 17:32 ` |FAILURE| " dpdklab
2024-06-06 17:32 ` dpdklab
2024-06-06 17:32 ` dpdklab
2024-06-06 17:32 ` |WARNING| " dpdklab
2024-06-06 17:32 ` |FAILURE| " dpdklab
2024-06-06 17:33 ` dpdklab
2024-06-06 17:33 ` |WARNING| " dpdklab
2024-06-06 17:33 ` |FAILURE| " dpdklab
2024-06-06 17:33 ` dpdklab
2024-06-06 17:33 ` dpdklab
2024-06-06 17:33 ` dpdklab
2024-06-06 17:34 ` dpdklab
2024-06-06 17:34 ` dpdklab
2024-06-06 17:34 ` dpdklab
2024-06-06 17:34 ` |WARNING| " dpdklab
2024-06-06 17:34 ` |FAILURE| " dpdklab
2024-06-06 17:35 ` dpdklab
2024-06-06 17:35 ` dpdklab
2024-06-06 17:35 ` dpdklab
2024-06-06 17:35 ` dpdklab
2024-06-06 17:35 ` dpdklab
2024-06-06 17:36 ` dpdklab
2024-06-06 17:36 ` dpdklab
2024-06-06 17:36 ` dpdklab
2024-06-06 17:36 ` dpdklab
2024-06-06 17:37 ` dpdklab
2024-06-06 17:37 ` dpdklab
2024-06-06 17:38 ` dpdklab
2024-06-06 17:38 ` dpdklab
2024-06-06 17:39 ` dpdklab
2024-06-06 17:40 ` |WARNING| " dpdklab
2024-06-06 17:41 ` |FAILURE| " dpdklab
2024-06-06 17:41 ` dpdklab
2024-06-06 17:58 ` dpdklab
2024-06-06 17:59 ` dpdklab
2024-06-06 18:02 ` dpdklab
2024-06-06 18:06 ` dpdklab
2024-06-06 18:30 ` |WARNING| " 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=6661f13f.050a0220.4c92a.628cSMTPIN_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).