From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135264 [PATCH] drivers: use dedicated logtypes
Date: Mon, 18 Dec 2023 07:06:02 -0800 (PST) [thread overview]
Message-ID: <65805fda.170a0220.60ac4.2609SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135264
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Monday, December 18 2023 13:59:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135264 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Fedora 38 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28658/
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-18 15:06 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 15:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 18:07 dpdklab
2023-12-18 16:12 dpdklab
2023-12-18 15:39 dpdklab
2023-12-18 15:33 dpdklab
2023-12-18 15:32 dpdklab
2023-12-18 15:31 dpdklab
2023-12-18 15:28 dpdklab
2023-12-18 15:28 dpdklab
2023-12-18 15:27 dpdklab
2023-12-18 15:24 dpdklab
2023-12-18 15:24 dpdklab
2023-12-18 15:22 dpdklab
2023-12-18 15:20 dpdklab
2023-12-18 15:19 dpdklab
2023-12-18 15:19 dpdklab
2023-12-18 15:18 dpdklab
2023-12-18 15:18 dpdklab
2023-12-18 15:16 dpdklab
2023-12-18 15:16 dpdklab
2023-12-18 15:14 dpdklab
2023-12-18 15:13 dpdklab
2023-12-18 15:12 dpdklab
2023-12-18 15:10 dpdklab
2023-12-18 15:10 dpdklab
2023-12-18 15:09 dpdklab
2023-12-18 15:09 dpdklab
2023-12-18 15:09 dpdklab
2023-12-18 15:08 dpdklab
2023-12-18 15:08 dpdklab
2023-12-18 15:06 dpdklab
2023-12-18 15:06 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:05 dpdklab
2023-12-18 15:04 dpdklab
2023-12-18 15:03 dpdklab
2023-12-18 15:03 dpdklab
2023-12-18 15:02 dpdklab
2023-12-18 15:01 dpdklab
2023-12-18 15:00 dpdklab
2023-12-18 15:00 dpdklab
2023-12-18 14:58 dpdklab
2023-12-18 14:58 dpdklab
2023-12-18 14:57 dpdklab
2023-12-18 14:57 dpdklab
2023-12-18 14:57 dpdklab
2023-12-18 14:56 dpdklab
2023-12-18 14:56 dpdklab
2023-12-18 14:56 dpdklab
2023-12-18 14:55 dpdklab
2023-12-18 14:55 dpdklab
2023-12-18 14:55 dpdklab
2023-12-18 14:53 dpdklab
2023-12-18 14:52 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:51 dpdklab
2023-12-18 14:50 dpdklab
2023-12-18 14:50 dpdklab
2023-12-18 14:50 dpdklab
2023-12-18 14:49 dpdklab
2023-12-18 14:48 dpdklab
2023-12-18 14:48 dpdklab
[not found] <20231218135932.1497163-1-david.marchand@redhat.com>
2023-12-18 13:40 ` qemudev
2023-12-18 13:45 ` qemudev
2023-12-18 14:00 ` checkpatch
2023-12-18 15:04 ` 0-day Robot
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=65805fda.170a0220.60ac4.2609SMTPIN_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).