From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw136339 [PATCH] drivers: Convert uses of RTE_LOG_DP to us
Date: Fri, 02 Feb 2024 10:52:50 -0800 (PST) [thread overview]
Message-ID: <65bd3a02.5d0a0220.cd813.4c84SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136339
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, February 02 2024 17:40:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a4ce111cc89f580b8c4aad51bdb061acbdfde86b
136339 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29043/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-02 18:52 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 18:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 22:15 dpdklab
2024-02-05 21:40 dpdklab
2024-02-05 20:36 dpdklab
2024-02-05 20:18 dpdklab
2024-02-05 20:17 dpdklab
2024-02-05 20:09 dpdklab
2024-02-05 20:01 dpdklab
2024-02-05 19:49 dpdklab
2024-02-05 19:47 dpdklab
2024-02-05 19:37 dpdklab
2024-02-05 19:32 dpdklab
2024-02-03 0:08 dpdklab
2024-02-02 23:33 dpdklab
2024-02-02 19:47 dpdklab
2024-02-02 19:05 dpdklab
2024-02-02 19:03 dpdklab
2024-02-02 19:03 dpdklab
2024-02-02 19:02 dpdklab
2024-02-02 19:01 dpdklab
2024-02-02 19:00 dpdklab
2024-02-02 18:56 dpdklab
2024-02-02 18:56 dpdklab
2024-02-02 18:56 dpdklab
2024-02-02 18:53 dpdklab
2024-02-02 18:51 dpdklab
2024-02-02 18:47 dpdklab
2024-02-02 18:46 dpdklab
2024-02-02 18:46 dpdklab
2024-02-02 18:45 dpdklab
2024-02-02 18:45 dpdklab
2024-02-02 18:45 dpdklab
2024-02-02 18:45 dpdklab
2024-02-02 18:45 dpdklab
2024-02-02 18:45 dpdklab
2024-02-02 18:44 dpdklab
2024-02-02 18:44 dpdklab
2024-02-02 18:44 dpdklab
2024-02-02 18:44 dpdklab
2024-02-02 18:44 dpdklab
2024-02-02 18:43 dpdklab
2024-02-02 18:43 dpdklab
2024-02-02 18:43 dpdklab
2024-02-02 18:43 dpdklab
2024-02-02 18:43 dpdklab
2024-02-02 18:42 dpdklab
2024-02-02 18:42 dpdklab
2024-02-02 18:42 dpdklab
2024-02-02 18:42 dpdklab
2024-02-02 18:41 dpdklab
2024-02-02 18:41 dpdklab
2024-02-02 18:41 dpdklab
2024-02-02 18:41 dpdklab
2024-02-02 18:40 dpdklab
2024-02-02 18:40 dpdklab
2024-02-02 18:40 dpdklab
2024-02-02 18:40 dpdklab
2024-02-02 18:39 dpdklab
2024-02-02 18:39 dpdklab
2024-02-02 18:39 dpdklab
2024-02-02 18:39 dpdklab
2024-02-02 18:38 dpdklab
2024-02-02 18:38 dpdklab
2024-02-02 18:38 dpdklab
2024-02-02 18:37 dpdklab
2024-02-02 18:37 dpdklab
2024-02-02 18:36 dpdklab
2024-02-02 18:36 dpdklab
2024-02-02 18:35 dpdklab
2024-02-02 18:34 dpdklab
2024-02-02 18:34 dpdklab
2024-02-02 18:33 dpdklab
2024-02-02 18:32 dpdklab
2024-02-02 18:31 dpdklab
2024-02-02 18: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=65bd3a02.5d0a0220.cd813.4c84SMTPIN_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).