From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133680 [PATCH] [v2] examples/l2fwd-macsec: add MACsec fo
Date: Tue, 31 Oct 2023 15:06:48 -0700 (PDT) [thread overview]
Message-ID: <65417a78.810a0220.48f69.4eb0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133680
_Testing PASS_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Tuesday, October 31 2023 18:44:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:32faaf30732cb4006cd1e45997403427029ef5fe
133680 --> testing pass
Test environment and result as below:
+---------------------+----------------------+--------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+======================+====================+
| Windows Server 2019 | PASS | PASS |
+---------------------+----------------------+--------------------+
| FreeBSD 13 | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
| Debian Buster | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
| CentOS Stream 8 | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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/28163/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-31 22:06 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 22:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 2:02 dpdklab
2023-11-01 1:58 dpdklab
2023-11-01 1:28 dpdklab
2023-11-01 0:59 dpdklab
2023-10-31 23:56 dpdklab
2023-10-31 23:56 dpdklab
2023-10-31 23:45 dpdklab
2023-10-31 23:44 dpdklab
2023-10-31 23:43 dpdklab
2023-10-31 23:13 dpdklab
2023-10-31 23:13 dpdklab
2023-10-31 23:07 dpdklab
2023-10-31 23:07 dpdklab
2023-10-31 23:06 dpdklab
2023-10-31 23:06 dpdklab
2023-10-31 23:05 dpdklab
2023-10-31 23:05 dpdklab
2023-10-31 23:04 dpdklab
2023-10-31 23:02 dpdklab
2023-10-31 23:02 dpdklab
2023-10-31 23:01 dpdklab
2023-10-31 23:00 dpdklab
2023-10-31 22:55 dpdklab
2023-10-31 22:51 dpdklab
2023-10-31 22:51 dpdklab
2023-10-31 22:50 dpdklab
2023-10-31 22:50 dpdklab
2023-10-31 22:50 dpdklab
2023-10-31 22:24 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:22 dpdklab
2023-10-31 22:20 dpdklab
2023-10-31 22:20 dpdklab
2023-10-31 22:19 dpdklab
2023-10-31 22:18 dpdklab
2023-10-31 22:12 dpdklab
2023-10-31 22:10 dpdklab
2023-10-31 22:08 dpdklab
2023-10-31 22:08 dpdklab
2023-10-31 22:08 dpdklab
2023-10-31 22:05 dpdklab
2023-10-31 22:04 dpdklab
2023-10-31 22:04 dpdklab
2023-10-31 22:04 dpdklab
2023-10-31 22:02 dpdklab
2023-10-31 22:02 dpdklab
2023-10-31 22:02 dpdklab
2023-10-31 22:01 dpdklab
2023-10-31 22: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=65417a78.810a0220.48f69.4eb0SMTPIN_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).