From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136818-136823 [PATCH] [v2,6/6] lpm: use rte atomic threa
Date: Thu, 15 Feb 2024 02:34:33 -0800 (PST) [thread overview]
Message-ID: <65cde8b9.4a0a0220.3621.3dc3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136823
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, February 15 2024 06:50:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62b906cf06ba86adf1f05c16969a9adcc49cf8bc
136818-136823 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| FreeBSD 13.2 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
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/29157/
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-15 10:34 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 10:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 13:51 dpdklab
2024-02-15 13:37 dpdklab
2024-02-15 13:19 dpdklab
2024-02-15 12:59 dpdklab
2024-02-15 12:57 dpdklab
2024-02-15 12:23 dpdklab
2024-02-15 12:20 dpdklab
2024-02-15 12:20 dpdklab
2024-02-15 12:18 dpdklab
2024-02-15 12:17 dpdklab
2024-02-15 11:52 dpdklab
2024-02-15 11:38 dpdklab
2024-02-15 11:35 dpdklab
2024-02-15 11:33 dpdklab
2024-02-15 11:32 dpdklab
2024-02-15 11:25 dpdklab
2024-02-15 11:21 dpdklab
2024-02-15 11:18 dpdklab
2024-02-15 11:18 dpdklab
2024-02-15 11:16 dpdklab
2024-02-15 11:16 dpdklab
2024-02-15 11:16 dpdklab
2024-02-15 11:15 dpdklab
2024-02-15 11:14 dpdklab
2024-02-15 11:13 dpdklab
2024-02-15 11:13 dpdklab
2024-02-15 11:12 dpdklab
2024-02-15 11:11 dpdklab
2024-02-15 11:11 dpdklab
2024-02-15 11:06 dpdklab
2024-02-15 11:05 dpdklab
2024-02-15 11:05 dpdklab
2024-02-15 11:04 dpdklab
2024-02-15 11:02 dpdklab
2024-02-15 11:02 dpdklab
2024-02-15 10:59 dpdklab
2024-02-15 10:58 dpdklab
2024-02-15 10:58 dpdklab
2024-02-15 10:57 dpdklab
2024-02-15 10:57 dpdklab
2024-02-15 10:56 dpdklab
2024-02-15 10:55 dpdklab
2024-02-15 10:54 dpdklab
2024-02-15 10:54 dpdklab
2024-02-15 10:54 dpdklab
2024-02-15 10:53 dpdklab
2024-02-15 10:53 dpdklab
2024-02-15 10:48 dpdklab
2024-02-15 10:48 dpdklab
2024-02-15 10:47 dpdklab
2024-02-15 10:46 dpdklab
2024-02-15 10:46 dpdklab
2024-02-15 10:46 dpdklab
2024-02-15 10:45 dpdklab
2024-02-15 10:45 dpdklab
2024-02-15 10:45 dpdklab
2024-02-15 10:45 dpdklab
2024-02-15 10:45 dpdklab
2024-02-15 10:44 dpdklab
2024-02-15 10:44 dpdklab
2024-02-15 10:44 dpdklab
2024-02-15 10:43 dpdklab
2024-02-15 10:43 dpdklab
2024-02-15 10:41 dpdklab
2024-02-15 10:41 dpdklab
2024-02-15 10:41 dpdklab
2024-02-15 10:40 dpdklab
2024-02-15 10:40 dpdklab
2024-02-15 10:35 dpdklab
2024-02-15 10:34 dpdklab
2024-02-15 10:33 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=65cde8b9.4a0a0220.3621.3dc3SMTPIN_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).