From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141294 [PATCH] memzone: remove unnecessary null checks
Date: Wed, 19 Jun 2024 00:16:33 -0700 (PDT) [thread overview]
Message-ID: <667285d1.170a0220.34b70.a89bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240618232508.21045-1-stephen@networkplumber.org>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141294
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, June 18 2024 23:25:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4cbeba6fdbc4d58da40c2051a8543ca69d2eac17
141294 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Debian 12 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL9 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Fedora 39 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 40 | PASS |
+------------------+----------+
| Ubuntu 24.04 | PASS |
+------------------+----------+
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
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
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 39
Kernel: Depends on container host
Compiler: clang 17.0.6
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30234/
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-19 7:17 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618232508.21045-1-stephen@networkplumber.org>
2024-06-18 22:58 ` qemudev
2024-06-18 23:03 ` qemudev
2024-06-18 23:26 ` checkpatch
2024-06-19 0:24 ` 0-day Robot
2024-06-19 3:07 ` dpdklab
2024-06-19 3:09 ` dpdklab
2024-06-19 3:11 ` dpdklab
2024-06-19 3:12 ` dpdklab
2024-06-19 3:22 ` dpdklab
2024-06-19 3:23 ` dpdklab
2024-06-19 3:23 ` dpdklab
2024-06-19 3:26 ` dpdklab
2024-06-19 3:28 ` dpdklab
2024-06-19 3:31 ` dpdklab
2024-06-19 3:32 ` dpdklab
2024-06-19 3:33 ` dpdklab
2024-06-19 3:33 ` dpdklab
2024-06-19 3:36 ` dpdklab
2024-06-19 3:45 ` dpdklab
2024-06-19 3:47 ` dpdklab
2024-06-19 4:36 ` dpdklab
2024-06-19 4:43 ` dpdklab
2024-06-19 4:45 ` dpdklab
2024-06-19 5:03 ` dpdklab
2024-06-19 5:11 ` dpdklab
2024-06-19 5:19 ` dpdklab
2024-06-19 5:21 ` dpdklab
2024-06-19 5:33 ` dpdklab
2024-06-19 7:06 ` dpdklab
2024-06-19 7:07 ` dpdklab
2024-06-19 7:08 ` dpdklab
2024-06-19 7:08 ` dpdklab
2024-06-19 7:15 ` dpdklab
2024-06-19 7:16 ` dpdklab
2024-06-19 7:16 ` dpdklab [this message]
2024-06-19 7:27 ` dpdklab
2024-06-19 7:32 ` dpdklab
2024-06-19 7:32 ` dpdklab
2024-06-19 7:34 ` dpdklab
2024-06-19 7:39 ` dpdklab
2024-06-19 7:52 ` dpdklab
2024-06-19 7:53 ` dpdklab
2024-06-19 7:56 ` dpdklab
2024-06-19 7:58 ` dpdklab
2024-06-19 8:06 ` dpdklab
2024-06-19 8:09 ` dpdklab
2024-06-19 8:10 ` dpdklab
2024-06-19 8:22 ` dpdklab
2024-06-19 8:23 ` dpdklab
2024-06-19 8:24 ` dpdklab
2024-06-19 8:29 ` dpdklab
2024-06-19 8:30 ` dpdklab
2024-06-19 8:35 ` dpdklab
2024-06-19 8:36 ` dpdklab
2024-06-19 8:37 ` dpdklab
2024-06-19 9:01 ` dpdklab
2024-06-19 9:03 ` dpdklab
2024-06-19 9:07 ` dpdklab
2024-06-19 9:14 ` dpdklab
2024-06-19 9:16 ` dpdklab
2024-06-19 10:53 ` dpdklab
2024-06-19 10:53 ` dpdklab
2024-06-19 10:55 ` dpdklab
2024-06-19 10:57 ` dpdklab
2024-06-19 10:57 ` dpdklab
2024-06-19 10:57 ` dpdklab
2024-06-19 10:58 ` dpdklab
2024-06-19 10:59 ` dpdklab
2024-06-19 10:59 ` dpdklab
2024-06-19 11:00 ` dpdklab
2024-06-19 11:00 ` dpdklab
2024-06-19 11:01 ` dpdklab
2024-06-19 11:01 ` dpdklab
2024-06-19 11:02 ` dpdklab
2024-06-19 11:04 ` dpdklab
2024-06-19 11:05 ` dpdklab
2024-06-19 11:09 ` dpdklab
2024-06-19 11:10 ` dpdklab
2024-06-19 11:10 ` dpdklab
2024-06-19 11:10 ` dpdklab
2024-06-19 11:10 ` dpdklab
2024-06-19 11:11 ` dpdklab
2024-06-19 11:11 ` dpdklab
2024-06-19 11:12 ` dpdklab
2024-06-19 11:12 ` dpdklab
2024-06-19 11:13 ` dpdklab
2024-06-19 11:13 ` dpdklab
2024-06-19 11:14 ` dpdklab
2024-06-19 11:22 ` dpdklab
2024-06-19 11:39 ` dpdklab
2024-06-19 11:39 ` dpdklab
2024-06-19 11:40 ` dpdklab
2024-06-19 11:42 ` dpdklab
2024-06-19 11:43 ` dpdklab
2024-06-19 11:44 ` dpdklab
2024-06-19 11:45 ` dpdklab
2024-06-19 11:47 ` dpdklab
2024-06-19 11:53 ` dpdklab
2024-06-19 11:54 ` dpdklab
2024-06-19 11:55 ` dpdklab
2024-06-19 11:58 ` dpdklab
2024-06-19 12:21 ` dpdklab
2024-06-19 12:23 ` dpdklab
2024-06-19 12:26 ` dpdklab
2024-06-19 12:26 ` dpdklab
2024-06-19 12:28 ` dpdklab
2024-06-19 12:29 ` dpdklab
2024-06-19 12:32 ` dpdklab
2024-06-19 12:33 ` dpdklab
2024-06-19 12:38 ` dpdklab
2024-06-19 12:56 ` dpdklab
2024-06-19 18:58 ` dpdklab
2024-06-19 19:14 ` dpdklab
2024-06-21 8:03 ` 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=667285d1.170a0220.34b70.a89bSMTPIN_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).