From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Jie Hai <haijie1@huawei.com>
Subject: |SUCCESS| pw137184-137188 [PATCH] [v4,7/7] net/hns3: support filter
Date: Sun, 25 Feb 2024 20:12:18 -0800 (PST) [thread overview]
Message-ID: <65dc0fa2.810a0220.20e45.0d14SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137188
_Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Monday, February 26 2024 03:07:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8c261a499faa28088489a141238f918be00807bb
137184-137188 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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/29254/
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-26 4:12 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 4:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 5:25 dpdklab
2024-02-26 4:54 dpdklab
2024-02-26 4:49 dpdklab
2024-02-26 4:48 dpdklab
2024-02-26 4:44 dpdklab
2024-02-26 4:38 dpdklab
2024-02-26 4:34 dpdklab
2024-02-26 4:33 dpdklab
2024-02-26 4:32 dpdklab
2024-02-26 4:30 dpdklab
2024-02-26 4:29 dpdklab
2024-02-26 4:29 dpdklab
2024-02-26 4:28 dpdklab
2024-02-26 4:26 dpdklab
2024-02-26 4:26 dpdklab
2024-02-26 4:25 dpdklab
2024-02-26 4:25 dpdklab
2024-02-26 4:23 dpdklab
2024-02-26 4:22 dpdklab
2024-02-26 4:22 dpdklab
2024-02-26 4:21 dpdklab
2024-02-26 4:17 dpdklab
2024-02-26 4:16 dpdklab
2024-02-26 4:14 dpdklab
2024-02-26 4:13 dpdklab
2024-02-26 4:13 dpdklab
2024-02-26 4:12 dpdklab
2024-02-26 4:12 dpdklab
2024-02-26 4:11 dpdklab
2024-02-26 4:10 dpdklab
2024-02-26 4:10 dpdklab
2024-02-26 4:10 dpdklab
2024-02-26 4:10 dpdklab
2024-02-26 4:09 dpdklab
2024-02-26 4:09 dpdklab
2024-02-26 4:08 dpdklab
2024-02-26 4:07 dpdklab
2024-02-26 4:06 dpdklab
2024-02-26 4:06 dpdklab
2024-02-26 4:05 dpdklab
2024-02-26 4:04 dpdklab
2024-02-26 4:03 dpdklab
2024-02-26 4:03 dpdklab
2024-02-26 4:02 dpdklab
2024-02-26 4:02 dpdklab
2024-02-26 4:01 dpdklab
2024-02-26 4:00 dpdklab
2024-02-26 3:59 dpdklab
2024-02-26 3:59 dpdklab
2024-02-26 3:58 dpdklab
2024-02-26 3:58 dpdklab
2024-02-26 3:57 dpdklab
2024-02-26 3:56 dpdklab
2024-02-26 3:56 dpdklab
2024-02-26 3:55 dpdklab
2024-02-26 3:55 dpdklab
2024-02-26 3:54 dpdklab
2024-02-26 3:54 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=65dc0fa2.810a0220.20e45.0d14SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=haijie1@huawei.com \
--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).