From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw134890 [PATCH] [RFT] net/nfb: use dynamic logtype
Date: Wed, 06 Dec 2023 20:49:16 -0800 (PST) [thread overview]
Message-ID: <65714ecc.170a0220.4614f.08c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134890
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, December 06 2023 17:51:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
134890 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Debian Bullseye | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28540/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-07 4:49 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 4:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 9:15 dpdklab
2023-12-07 6:08 dpdklab
2023-12-07 5:53 dpdklab
2023-12-07 5:33 dpdklab
2023-12-07 5:32 dpdklab
2023-12-07 5:22 dpdklab
2023-12-07 5:21 dpdklab
2023-12-07 5:21 dpdklab
2023-12-07 5:20 dpdklab
2023-12-07 5:19 dpdklab
2023-12-07 5:07 dpdklab
2023-12-07 5:07 dpdklab
2023-12-07 5:07 dpdklab
2023-12-07 5:06 dpdklab
2023-12-07 5:06 dpdklab
2023-12-07 5:04 dpdklab
2023-12-07 4:49 dpdklab
2023-12-07 4:49 dpdklab
2023-12-07 4:48 dpdklab
2023-12-07 4:48 dpdklab
2023-12-07 4:48 dpdklab
2023-12-07 4:48 dpdklab
2023-12-07 4:47 dpdklab
2023-12-07 4:47 dpdklab
2023-12-07 4:47 dpdklab
2023-12-07 4:47 dpdklab
2023-12-07 4:46 dpdklab
2023-12-07 4:46 dpdklab
2023-12-07 4:45 dpdklab
2023-12-07 4:44 dpdklab
2023-12-07 4:43 dpdklab
2023-12-07 4:43 dpdklab
2023-12-07 4:43 dpdklab
2023-12-07 4:42 dpdklab
2023-12-07 4:42 dpdklab
2023-12-07 4:42 dpdklab
2023-12-07 4:41 dpdklab
2023-12-07 4:40 dpdklab
2023-12-07 4:40 dpdklab
2023-12-07 4:40 dpdklab
2023-12-07 4:40 dpdklab
2023-12-07 4:37 dpdklab
2023-12-07 4:37 dpdklab
2023-12-07 4:36 dpdklab
2023-12-07 4:36 dpdklab
2023-12-07 4:36 dpdklab
2023-12-07 4:36 dpdklab
2023-12-07 4:35 dpdklab
2023-12-07 4:35 dpdklab
2023-12-07 4:35 dpdklab
2023-12-07 4:35 dpdklab
2023-12-07 4:34 dpdklab
2023-12-07 4:34 dpdklab
2023-12-07 4:33 dpdklab
2023-12-07 4:27 dpdklab
2023-12-07 4:27 dpdklab
2023-12-07 4:26 dpdklab
2023-12-07 4:26 dpdklab
2023-12-07 4:26 dpdklab
2023-12-07 4:25 dpdklab
2023-12-07 4:25 dpdklab
2023-12-07 4:21 dpdklab
2023-12-07 4:15 dpdklab
2023-12-07 4:01 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=65714ecc.170a0220.4614f.08c5SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).