From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142171 [PATCH] net/mlx5: fix compilation warning in GCC-
Date: Sun, 07 Jul 2024 23:37:53 -0700 (PDT) [thread overview]
Message-ID: <668b8941.050a0220.9cdc6.0165SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240707095723.46947-1-getelson@nvidia.com>
Test-Label: iol-abi-testing
Test-Status: PENDING
http://dpdk.org/patch/142171
_Testing pending_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sunday, July 07 2024 09:57:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b31811d96c1d0fb36df78dc34ef8325bce447bfc
142171 --> testing pending
Test environment and result as below:
+-------------------+----------+
| Environment | abi_test |
+===================+==========+
| CentOS Stream 8 | PASS |
+-------------------+----------+
| Debian 12 | PASS |
+-------------------+----------+
| CentOS Stream 9 | PASS |
+-------------------+----------+
| Debian Bullseye | PASS |
+-------------------+----------+
| Fedora 38 (Clang) | PASS |
+-------------------+----------+
| Fedora 37 | PASS |
+-------------------+----------+
| Fedora 39 (Clang) | PASS |
+-------------------+----------+
| Fedora 38 | PEND |
+-------------------+----------+
| Fedora 39 | PASS |
+-------------------+----------+
| Fedora 40 (Clang) | PASS |
+-------------------+----------+
| openSUSE Leap 15 | PASS |
+-------------------+----------+
| Fedora 40 | PEND |
+-------------------+----------+
| Ubuntu 24.04 | PEND |
+-------------------+----------+
| Ubuntu 22.04 | PASS |
+-------------------+----------+
| RHEL8 | PASS |
+-------------------+----------+
| RHEL9 | PEND |
+-------------------+----------+
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
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
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30442/
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-07-08 6:38 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240707095723.46947-1-getelson@nvidia.com>
2024-07-07 9:34 ` |SUCCESS| pw142171 [PATCH] net/mlx5: fix compilation warning in GCC-9.1 qemudev
2024-07-07 9:39 ` qemudev
2024-07-07 9:59 ` checkpatch
2024-07-07 10:43 ` 0-day Robot
2024-07-08 6:15 ` |PENDING| pw142171 [PATCH] net/mlx5: fix compilation warning in GCC- dpdklab
2024-07-08 6:19 ` dpdklab
2024-07-08 6:23 ` dpdklab
2024-07-08 6:24 ` dpdklab
2024-07-08 6:26 ` dpdklab
2024-07-08 6:27 ` dpdklab
2024-07-08 6:27 ` dpdklab
2024-07-08 6:29 ` |SUCCESS| " dpdklab
2024-07-08 6:29 ` |PENDING| " dpdklab
2024-07-08 6:30 ` dpdklab
2024-07-08 6:36 ` |SUCCESS| " dpdklab
2024-07-08 6:37 ` |PENDING| " dpdklab
2024-07-08 6:37 ` dpdklab [this message]
2024-07-08 6:39 ` |SUCCESS| " dpdklab
2024-07-08 6:42 ` |PENDING| " dpdklab
2024-07-08 6:43 ` dpdklab
2024-07-08 6:45 ` dpdklab
2024-07-08 6:47 ` dpdklab
2024-07-08 6:48 ` dpdklab
2024-07-08 6:50 ` |SUCCESS| " dpdklab
2024-07-08 6:50 ` |PENDING| " dpdklab
2024-07-08 6:51 ` dpdklab
2024-07-08 6:51 ` dpdklab
2024-07-08 6:53 ` |SUCCESS| " dpdklab
2024-07-08 6:56 ` |PENDING| " dpdklab
2024-07-08 6:59 ` |SUCCESS| " dpdklab
2024-07-08 7:14 ` |PENDING| " dpdklab
2024-07-08 7:15 ` dpdklab
2024-07-08 7:21 ` |SUCCESS| " dpdklab
2024-07-08 7:56 ` |PENDING| " dpdklab
2024-07-08 8:13 ` dpdklab
2024-07-08 8:21 ` |SUCCESS| " dpdklab
2024-07-08 8:57 ` dpdklab
2024-07-08 10:12 ` dpdklab
2024-07-08 10:17 ` dpdklab
2024-07-08 10:47 ` dpdklab
2024-07-08 11:21 ` dpdklab
2024-07-08 11:24 ` |PENDING| " dpdklab
2024-07-08 11:31 ` dpdklab
2024-07-08 11:35 ` dpdklab
2024-07-08 11:36 ` dpdklab
2024-07-08 11:37 ` dpdklab
2024-07-08 11:38 ` dpdklab
2024-07-08 11:39 ` |SUCCESS| " dpdklab
2024-07-08 11:40 ` |PENDING| " dpdklab
2024-07-08 11:47 ` dpdklab
2024-07-08 11:48 ` dpdklab
2024-07-08 11:48 ` dpdklab
2024-07-08 11:51 ` dpdklab
2024-07-08 11:52 ` dpdklab
2024-07-08 11:52 ` dpdklab
2024-07-08 11:56 ` dpdklab
2024-07-08 11:57 ` dpdklab
2024-07-08 12:06 ` dpdklab
2024-07-08 12:09 ` |SUCCESS| " dpdklab
2024-07-08 12:11 ` |PENDING| " dpdklab
2024-07-08 12:39 ` dpdklab
2024-07-08 12:39 ` dpdklab
2024-07-08 12:42 ` dpdklab
2024-07-08 12:46 ` dpdklab
2024-07-08 12:57 ` dpdklab
2024-07-08 13:01 ` dpdklab
2024-07-08 13:03 ` dpdklab
2024-07-08 13:05 ` dpdklab
2024-07-08 13:06 ` dpdklab
2024-07-08 13:09 ` dpdklab
2024-07-08 13:10 ` dpdklab
2024-07-08 13:12 ` dpdklab
2024-07-08 13:14 ` dpdklab
2024-07-08 13:15 ` dpdklab
2024-07-08 13:17 ` dpdklab
2024-07-08 13:19 ` dpdklab
2024-07-08 13:26 ` dpdklab
2024-07-08 13:32 ` dpdklab
2024-07-08 13:45 ` dpdklab
2024-07-08 13:54 ` |SUCCESS| " dpdklab
2024-07-08 20:32 ` dpdklab
2024-07-09 14:16 ` dpdklab
2024-07-09 14:29 ` dpdklab
2024-07-13 21:40 ` dpdklab
2024-07-14 10:36 ` dpdklab
2024-07-14 17:10 ` dpdklab
2024-07-15 9:24 ` dpdklab
2024-07-15 9: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=668b8941.050a0220.9cdc6.0165SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).