From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136994 [PATCH] raw/cnxk_bphy: use standard log calls
Date: Thu, 22 Feb 2024 03:58:38 -0800 (PST) [thread overview]
Message-ID: <65d736ee.050a0220.24b68.e024SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136994
_Testing PASS_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Thursday, February 22 2024 09:13:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
136994 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29219/
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-22 11:58 UTC|newest]
Thread overview: 139+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 11:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-24 0:28 dpdklab
2024-02-23 23:45 dpdklab
2024-02-23 18:52 dpdklab
2024-02-23 3:53 dpdklab
2024-02-23 3:45 dpdklab
2024-02-23 3:40 dpdklab
2024-02-23 3:33 dpdklab
2024-02-22 14:47 dpdklab
2024-02-22 14:34 dpdklab
2024-02-22 14:33 dpdklab
2024-02-22 14:30 dpdklab
2024-02-22 14:26 dpdklab
2024-02-22 14:07 dpdklab
2024-02-22 14:07 dpdklab
2024-02-22 14:06 dpdklab
2024-02-22 13:55 dpdklab
2024-02-22 13:53 dpdklab
2024-02-22 13:51 dpdklab
2024-02-22 13:47 dpdklab
2024-02-22 13:46 dpdklab
2024-02-22 13:39 dpdklab
2024-02-22 13:39 dpdklab
2024-02-22 13:38 dpdklab
2024-02-22 13:32 dpdklab
2024-02-22 13:31 dpdklab
2024-02-22 13:30 dpdklab
2024-02-22 13:27 dpdklab
2024-02-22 13:26 dpdklab
2024-02-22 13:24 dpdklab
2024-02-22 13:24 dpdklab
2024-02-22 13:19 dpdklab
2024-02-22 13:15 dpdklab
2024-02-22 13:14 dpdklab
2024-02-22 13:08 dpdklab
2024-02-22 13:07 dpdklab
2024-02-22 13:00 dpdklab
2024-02-22 12:59 dpdklab
2024-02-22 12:58 dpdklab
2024-02-22 12:58 dpdklab
2024-02-22 12:54 dpdklab
2024-02-22 12:44 dpdklab
2024-02-22 12:43 dpdklab
2024-02-22 12:43 dpdklab
2024-02-22 12:41 dpdklab
2024-02-22 12:38 dpdklab
2024-02-22 12:37 dpdklab
2024-02-22 12:37 dpdklab
2024-02-22 12:36 dpdklab
2024-02-22 12:36 dpdklab
2024-02-22 12:35 dpdklab
2024-02-22 12:35 dpdklab
2024-02-22 12:34 dpdklab
2024-02-22 12:33 dpdklab
2024-02-22 12:31 dpdklab
2024-02-22 12:30 dpdklab
2024-02-22 12:30 dpdklab
2024-02-22 12:27 dpdklab
2024-02-22 12:27 dpdklab
2024-02-22 12:27 dpdklab
2024-02-22 12:26 dpdklab
2024-02-22 12:26 dpdklab
2024-02-22 12:26 dpdklab
2024-02-22 12:25 dpdklab
2024-02-22 12:25 dpdklab
2024-02-22 12:25 dpdklab
2024-02-22 12:25 dpdklab
2024-02-22 12:24 dpdklab
2024-02-22 12:24 dpdklab
2024-02-22 12:23 dpdklab
2024-02-22 12:23 dpdklab
2024-02-22 12:22 dpdklab
2024-02-22 12:21 dpdklab
2024-02-22 12:20 dpdklab
2024-02-22 12:20 dpdklab
2024-02-22 12:20 dpdklab
2024-02-22 12:19 dpdklab
2024-02-22 12:19 dpdklab
2024-02-22 12:18 dpdklab
2024-02-22 12:18 dpdklab
2024-02-22 12:18 dpdklab
2024-02-22 12:16 dpdklab
2024-02-22 12:06 dpdklab
2024-02-22 12:06 dpdklab
2024-02-22 12:06 dpdklab
2024-02-22 12:06 dpdklab
2024-02-22 12:05 dpdklab
2024-02-22 12:05 dpdklab
2024-02-22 12:05 dpdklab
2024-02-22 12:05 dpdklab
2024-02-22 12:04 dpdklab
2024-02-22 12:04 dpdklab
2024-02-22 12:04 dpdklab
2024-02-22 12:04 dpdklab
2024-02-22 12:03 dpdklab
2024-02-22 12:02 dpdklab
2024-02-22 12:02 dpdklab
2024-02-22 12:02 dpdklab
2024-02-22 12:02 dpdklab
2024-02-22 12:02 dpdklab
2024-02-22 12:02 dpdklab
2024-02-22 12:01 dpdklab
2024-02-22 12:00 dpdklab
2024-02-22 12:00 dpdklab
2024-02-22 12:00 dpdklab
2024-02-22 11:59 dpdklab
2024-02-22 11:59 dpdklab
2024-02-22 11:59 dpdklab
2024-02-22 11:59 dpdklab
2024-02-22 11:58 dpdklab
2024-02-22 11:58 dpdklab
2024-02-22 11:58 dpdklab
2024-02-22 11:56 dpdklab
2024-02-22 11:48 dpdklab
2024-02-22 11:48 dpdklab
2024-02-22 11:47 dpdklab
2024-02-22 11:47 dpdklab
2024-02-22 11:47 dpdklab
2024-02-22 11:40 dpdklab
2024-02-22 11:40 dpdklab
2024-02-22 11:40 dpdklab
2024-02-22 11:39 dpdklab
2024-02-22 11:38 dpdklab
2024-02-22 11:38 dpdklab
2024-02-22 11:38 dpdklab
2024-02-22 11:38 dpdklab
2024-02-22 11:37 dpdklab
2024-02-22 11:37 dpdklab
2024-02-22 11:37 dpdklab
2024-02-22 11:37 dpdklab
2024-02-22 11:37 dpdklab
2024-02-22 11:37 dpdklab
2024-02-22 11:35 dpdklab
2024-02-22 11:34 dpdklab
2024-02-22 11:34 dpdklab
[not found] <20240222091313.4030144-1-tduszynski@marvell.com>
2024-02-22 8:50 ` qemudev
2024-02-22 8:55 ` qemudev
2024-02-22 9:14 ` checkpatch
2024-02-22 10: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=65d736ee.050a0220.24b68.e024SMTPIN_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).