From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136380 [PATCH] net/hns3: support power monitor
Date: Mon, 05 Feb 2024 01:19:02 -0800 (PST) [thread overview]
Message-ID: <65c0a806.050a0220.94b4f.3269SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136380
_Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Monday, February 05 2024 08:35:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f8ecc0053ca52cb2310a9e1834ea583167a793cd
136380 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29048/
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-05 9:19 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 9:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 11:13 dpdklab
2024-02-05 10:39 dpdklab
2024-02-05 10:32 dpdklab
2024-02-05 10:11 dpdklab
2024-02-05 10:08 dpdklab
2024-02-05 10:02 dpdklab
2024-02-05 10:01 dpdklab
2024-02-05 10:01 dpdklab
2024-02-05 9:58 dpdklab
2024-02-05 9:56 dpdklab
2024-02-05 9:55 dpdklab
2024-02-05 9:53 dpdklab
2024-02-05 9:52 dpdklab
2024-02-05 9:50 dpdklab
2024-02-05 9:48 dpdklab
2024-02-05 9:48 dpdklab
2024-02-05 9:47 dpdklab
2024-02-05 9:44 dpdklab
2024-02-05 9:44 dpdklab
2024-02-05 9:43 dpdklab
2024-02-05 9:42 dpdklab
2024-02-05 9:41 dpdklab
2024-02-05 9:37 dpdklab
2024-02-05 9:36 dpdklab
2024-02-05 9:36 dpdklab
2024-02-05 9:36 dpdklab
2024-02-05 9:35 dpdklab
2024-02-05 9:34 dpdklab
2024-02-05 9:33 dpdklab
2024-02-05 9:31 dpdklab
2024-02-05 9:31 dpdklab
2024-02-05 9:29 dpdklab
2024-02-05 9:29 dpdklab
2024-02-05 9:28 dpdklab
2024-02-05 9:27 dpdklab
2024-02-05 9:27 dpdklab
2024-02-05 9:26 dpdklab
2024-02-05 9:26 dpdklab
2024-02-05 9:26 dpdklab
2024-02-05 9:25 dpdklab
2024-02-05 9:24 dpdklab
2024-02-05 9:24 dpdklab
2024-02-05 9:23 dpdklab
2024-02-05 9:23 dpdklab
2024-02-05 9:23 dpdklab
2024-02-05 9:22 dpdklab
2024-02-05 9:21 dpdklab
2024-02-05 9:21 dpdklab
2024-02-05 9:20 dpdklab
2024-02-05 9:20 dpdklab
2024-02-05 9:20 dpdklab
2024-02-05 9:19 dpdklab
2024-02-05 9:19 dpdklab
2024-02-05 9:18 dpdklab
2024-02-05 9:18 dpdklab
2024-02-05 9:18 dpdklab
2024-02-05 9:17 dpdklab
2024-02-05 9:17 dpdklab
2024-02-05 9:17 dpdklab
2024-02-05 9:17 dpdklab
2024-02-05 9:16 dpdklab
2024-02-05 9:16 dpdklab
2024-02-05 9:16 dpdklab
2024-02-05 9:15 dpdklab
2024-02-05 9:15 dpdklab
[not found] <20240205083521.3782951-1-haijie1@huawei.com>
2024-02-05 8:16 ` qemudev
2024-02-05 8:20 ` qemudev
2024-02-05 8:41 ` checkpatch
2024-02-05 9:44 ` 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=65c0a806.050a0220.94b4f.3269SMTPIN_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).