From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141275 [PATCH] [v4] net: add bit fields to IPv6 header d
Date: Tue, 18 Jun 2024 13:22:53 -0700 (PDT) [thread overview]
Message-ID: <6671ec9d.050a0220.1aec91.4c1dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240618121841.10070-1-getelson@nvidia.com>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141275
_Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, June 18 2024 12:18:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:567bb951716f1ae9e418eacda3dd9dac5edf6fde
141275 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Fedora 38 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Fedora 39 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Fedora 40 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Ubuntu 24.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL9 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Debian 12 | PASS |
+------------------+----------+
Fedora 38
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
Kernel: Depends on container host
Compiler: gcc 13.2.1
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 40
Kernel: Depends on container host
Compiler: clang 18.1.6
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
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30224/
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-18 20:22 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618121841.10070-1-getelson@nvidia.com>
2024-06-18 11:52 ` |SUCCESS| pw141275 [PATCH v4] net: add bit fields to IPv6 header definition qemudev
2024-06-18 11:57 ` qemudev
2024-06-18 12:21 ` checkpatch
2024-06-18 13:05 ` 0-day Robot
2024-06-18 17:20 ` |SUCCESS| pw141275 [PATCH] [v4] net: add bit fields to IPv6 header d dpdklab
2024-06-18 17:27 ` dpdklab
2024-06-18 17:27 ` dpdklab
2024-06-18 17:28 ` dpdklab
2024-06-18 17:28 ` dpdklab
2024-06-18 17:28 ` dpdklab
2024-06-18 17:29 ` dpdklab
2024-06-18 17:29 ` dpdklab
2024-06-18 17:30 ` dpdklab
2024-06-18 17:30 ` dpdklab
2024-06-18 17:31 ` dpdklab
2024-06-18 17:37 ` dpdklab
2024-06-18 17:37 ` dpdklab
2024-06-18 17:38 ` dpdklab
2024-06-18 17:39 ` dpdklab
2024-06-18 17:44 ` dpdklab
2024-06-18 19:36 ` dpdklab
2024-06-18 19:37 ` dpdklab
2024-06-18 19:38 ` dpdklab
2024-06-18 19:39 ` dpdklab
2024-06-18 19:39 ` dpdklab
2024-06-18 19:40 ` dpdklab
2024-06-18 19:40 ` dpdklab
2024-06-18 20:05 ` dpdklab
2024-06-18 20:06 ` dpdklab
2024-06-18 20:07 ` dpdklab
2024-06-18 20:07 ` dpdklab
2024-06-18 20:08 ` dpdklab
2024-06-18 20:09 ` dpdklab
2024-06-18 20:14 ` dpdklab
2024-06-18 20:15 ` dpdklab
2024-06-18 20:16 ` dpdklab
2024-06-18 20:19 ` dpdklab
2024-06-18 20:20 ` dpdklab
2024-06-18 20:21 ` dpdklab
2024-06-18 20:21 ` dpdklab
2024-06-18 20:22 ` dpdklab [this message]
2024-06-18 20:24 ` dpdklab
2024-06-18 21:38 ` dpdklab
2024-06-18 21:47 ` dpdklab
2024-06-18 21:49 ` dpdklab
2024-06-18 21:50 ` dpdklab
2024-06-18 21:51 ` dpdklab
2024-06-18 21:52 ` dpdklab
2024-06-18 21:53 ` dpdklab
2024-06-18 21:55 ` dpdklab
2024-06-18 22:01 ` dpdklab
2024-06-18 22:03 ` dpdklab
2024-06-18 22:04 ` dpdklab
2024-06-18 22:07 ` dpdklab
2024-06-18 22:07 ` dpdklab
2024-06-18 22:23 ` dpdklab
2024-06-18 22:24 ` dpdklab
2024-06-18 22:24 ` dpdklab
2024-06-18 22:27 ` dpdklab
2024-06-18 22:28 ` dpdklab
2024-06-18 22:33 ` dpdklab
2024-06-18 22:34 ` dpdklab
2024-06-18 22:36 ` dpdklab
2024-06-18 22:39 ` dpdklab
2024-06-18 22:40 ` dpdklab
2024-06-18 22:40 ` dpdklab
2024-06-18 22:41 ` dpdklab
2024-06-18 22:44 ` dpdklab
2024-06-18 22:46 ` dpdklab
2024-06-18 22:46 ` dpdklab
2024-06-18 22:47 ` dpdklab
2024-06-18 22:47 ` dpdklab
2024-06-18 22:48 ` dpdklab
2024-06-18 22:48 ` dpdklab
2024-06-18 22:48 ` dpdklab
2024-06-18 22:49 ` dpdklab
2024-06-18 22:49 ` dpdklab
2024-06-18 22:50 ` dpdklab
2024-06-18 23:00 ` dpdklab
2024-06-18 23:00 ` dpdklab
2024-06-18 23:01 ` dpdklab
2024-06-18 23:02 ` dpdklab
2024-06-18 23:02 ` dpdklab
2024-06-18 23:04 ` dpdklab
2024-06-18 23:11 ` dpdklab
2024-06-18 23:23 ` dpdklab
2024-06-18 23:27 ` dpdklab
2024-06-18 23:27 ` dpdklab
2024-06-18 23:29 ` dpdklab
2024-06-18 23:29 ` dpdklab
2024-06-18 23:30 ` dpdklab
2024-06-18 23:30 ` dpdklab
2024-06-18 23:30 ` dpdklab
2024-06-18 23:30 ` dpdklab
2024-06-18 23:37 ` dpdklab
2024-06-18 23:37 ` dpdklab
2024-06-18 23:37 ` dpdklab
2024-06-18 23:38 ` dpdklab
2024-06-18 23:49 ` dpdklab
2024-06-18 23:50 ` dpdklab
2024-06-19 0:02 ` dpdklab
2024-06-19 0:11 ` dpdklab
2024-06-19 0:13 ` dpdklab
2024-06-19 0:14 ` dpdklab
2024-06-19 0:17 ` dpdklab
2024-06-19 0:18 ` dpdklab
2024-06-19 0:26 ` dpdklab
2024-06-19 0:28 ` dpdklab
2024-06-19 0:33 ` dpdklab
2024-06-19 1:03 ` dpdklab
2024-06-19 6:28 ` dpdklab
2024-06-19 7:29 ` dpdklab
2024-06-20 2:58 ` 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=6671ec9d.050a0220.1aec91.4c1dSMTPIN_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).