From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136898-136903 [PATCH] [v3,7/7] net/hns3: support filter
Date: Tue, 20 Feb 2024 05:27:51 -0800 (PST) [thread overview]
Message-ID: <65d4a8d7.050a0220.75777.12f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136903
_Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Tuesday, February 20 2024 10:58:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa24b3f588b31ee9699f6b2dde8d12c0453448d1
136898-136903 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29190/
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-20 13:27 UTC|newest]
Thread overview: 122+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 13:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 4:50 dpdklab
2024-02-21 4:42 dpdklab
2024-02-21 4:34 dpdklab
2024-02-21 4:27 dpdklab
2024-02-20 20:26 dpdklab
2024-02-20 19:58 dpdklab
2024-02-20 19:38 dpdklab
2024-02-20 19:16 dpdklab
2024-02-20 18:57 dpdklab
2024-02-20 18:28 dpdklab
2024-02-20 18:07 dpdklab
2024-02-20 16:39 dpdklab
2024-02-20 16:35 dpdklab
2024-02-20 16:33 dpdklab
2024-02-20 16:18 dpdklab
2024-02-20 16:18 dpdklab
2024-02-20 16:17 dpdklab
2024-02-20 16:11 dpdklab
2024-02-20 16:09 dpdklab
2024-02-20 16:08 dpdklab
2024-02-20 16:07 dpdklab
2024-02-20 16:07 dpdklab
2024-02-20 16:00 dpdklab
2024-02-20 15:43 dpdklab
2024-02-20 15:42 dpdklab
2024-02-20 15:40 dpdklab
2024-02-20 15:39 dpdklab
2024-02-20 15:38 dpdklab
2024-02-20 15:37 dpdklab
2024-02-20 15:37 dpdklab
2024-02-20 15:36 dpdklab
2024-02-20 15:33 dpdklab
2024-02-20 15:27 dpdklab
2024-02-20 15:23 dpdklab
2024-02-20 15:23 dpdklab
2024-02-20 15:09 dpdklab
2024-02-20 15:09 dpdklab
2024-02-20 15:09 dpdklab
2024-02-20 15:08 dpdklab
2024-02-20 15:08 dpdklab
2024-02-20 15:04 dpdklab
2024-02-20 14:51 dpdklab
2024-02-20 14:50 dpdklab
2024-02-20 14:49 dpdklab
2024-02-20 14:49 dpdklab
2024-02-20 14:42 dpdklab
2024-02-20 14:39 dpdklab
2024-02-20 14:38 dpdklab
2024-02-20 14:38 dpdklab
2024-02-20 14:31 dpdklab
2024-02-20 14:30 dpdklab
2024-02-20 14:23 dpdklab
2024-02-20 14:22 dpdklab
2024-02-20 14:22 dpdklab
2024-02-20 14:22 dpdklab
2024-02-20 14:19 dpdklab
2024-02-20 14:16 dpdklab
2024-02-20 14:14 dpdklab
2024-02-20 14:11 dpdklab
2024-02-20 14:10 dpdklab
2024-02-20 14:10 dpdklab
2024-02-20 14:09 dpdklab
2024-02-20 14:08 dpdklab
2024-02-20 14:07 dpdklab
2024-02-20 14:07 dpdklab
2024-02-20 14:07 dpdklab
2024-02-20 14:07 dpdklab
2024-02-20 14:06 dpdklab
2024-02-20 14:06 dpdklab
2024-02-20 14:05 dpdklab
2024-02-20 14:04 dpdklab
2024-02-20 14:03 dpdklab
2024-02-20 14:03 dpdklab
2024-02-20 14:02 dpdklab
2024-02-20 14:00 dpdklab
2024-02-20 13:58 dpdklab
2024-02-20 13:57 dpdklab
2024-02-20 13:56 dpdklab
2024-02-20 13:54 dpdklab
2024-02-20 13:54 dpdklab
2024-02-20 13:53 dpdklab
2024-02-20 13:51 dpdklab
2024-02-20 13:51 dpdklab
2024-02-20 13:50 dpdklab
2024-02-20 13:48 dpdklab
2024-02-20 13:45 dpdklab
2024-02-20 13:44 dpdklab
2024-02-20 13:41 dpdklab
2024-02-20 13:38 dpdklab
2024-02-20 13:38 dpdklab
2024-02-20 13:35 dpdklab
2024-02-20 13:30 dpdklab
2024-02-20 13:25 dpdklab
2024-02-20 13:18 dpdklab
2024-02-20 13:15 dpdklab
2024-02-20 13:10 dpdklab
2024-02-20 13:10 dpdklab
2024-02-20 13:10 dpdklab
2024-02-20 13:09 dpdklab
2024-02-20 13:03 dpdklab
2024-02-20 13:02 dpdklab
2024-02-20 13:01 dpdklab
2024-02-20 13:01 dpdklab
2024-02-20 13:00 dpdklab
2024-02-20 13:00 dpdklab
2024-02-20 13:00 dpdklab
2024-02-20 12:59 dpdklab
2024-02-20 12:53 dpdklab
2024-02-20 12:52 dpdklab
2024-02-20 12:51 dpdklab
2024-02-20 12:51 dpdklab
2024-02-20 12:49 dpdklab
2024-02-20 12:49 dpdklab
2024-02-20 12:48 dpdklab
2024-02-20 12:47 dpdklab
2024-02-20 12:47 dpdklab
2024-02-20 12:47 dpdklab
2024-02-20 12:46 dpdklab
2024-02-20 12:46 dpdklab
2024-02-20 12:46 dpdklab
2024-02-20 12:35 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=65d4a8d7.050a0220.75777.12f8SMTPIN_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).