From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135721 [PATCH] [v2] app/test-crypto-perf: fix invalid mb
Date: Wed, 03 Jan 2024 19:07:26 -0800 (PST) [thread overview]
Message-ID: <659620ee.050a0220.3d791.68f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135721
_Testing PASS_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Thursday, January 04 2024 02:24:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135721 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28784/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-04 3:07 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 3:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 0:23 dpdklab
2024-01-05 0:13 dpdklab
2024-01-04 21:40 dpdklab
2024-01-04 10:20 dpdklab
2024-01-04 10:17 dpdklab
2024-01-04 10:14 dpdklab
2024-01-04 10:13 dpdklab
2024-01-04 10:12 dpdklab
2024-01-04 10:11 dpdklab
2024-01-04 10:10 dpdklab
2024-01-04 10:09 dpdklab
2024-01-04 10:08 dpdklab
2024-01-04 10:08 dpdklab
2024-01-04 10:06 dpdklab
2024-01-04 9:49 dpdklab
2024-01-04 9:48 dpdklab
2024-01-04 9:48 dpdklab
2024-01-04 9:47 dpdklab
2024-01-04 9:45 dpdklab
2024-01-04 9:42 dpdklab
2024-01-04 9:35 dpdklab
2024-01-04 9:33 dpdklab
2024-01-04 9:30 dpdklab
2024-01-04 9:27 dpdklab
2024-01-04 9:23 dpdklab
2024-01-04 9:03 dpdklab
2024-01-04 8:55 dpdklab
2024-01-04 8:52 dpdklab
2024-01-04 8:47 dpdklab
2024-01-04 8:42 dpdklab
2024-01-04 8:34 dpdklab
2024-01-04 8:28 dpdklab
2024-01-04 8:28 dpdklab
2024-01-04 8:12 dpdklab
2024-01-04 8:07 dpdklab
2024-01-04 7:54 dpdklab
2024-01-04 7:13 dpdklab
2024-01-04 7:11 dpdklab
2024-01-04 7:11 dpdklab
2024-01-04 7:10 dpdklab
2024-01-04 7:10 dpdklab
2024-01-04 7:10 dpdklab
2024-01-04 7:09 dpdklab
2024-01-04 7:08 dpdklab
2024-01-04 4:01 dpdklab
2024-01-04 3:37 dpdklab
2024-01-04 3:30 dpdklab
2024-01-04 3:26 dpdklab
2024-01-04 3:19 dpdklab
2024-01-04 3:16 dpdklab
2024-01-04 3:15 dpdklab
2024-01-04 3:11 dpdklab
2024-01-04 3:11 dpdklab
2024-01-04 3:11 dpdklab
2024-01-04 3:11 dpdklab
2024-01-04 3:11 dpdklab
2024-01-04 3:08 dpdklab
2024-01-04 3:08 dpdklab
2024-01-04 3:07 dpdklab
2024-01-04 3:06 dpdklab
2024-01-04 3:01 dpdklab
2024-01-04 3:00 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=659620ee.050a0220.3d791.68f4SMTPIN_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).