From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132300-132301 [PATCH] [v2,2/2] common/cnxk: fix direct r
Date: Wed, 04 Oct 2023 06:06:40 -0700 (PDT) [thread overview]
Message-ID: <651d6360.050a0220.d77ea.6f1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132301
_Testing PASS_
Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Wednesday, October 04 2023 12:24:32
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: master
CommitID:aa2ba6981f60d7f97d81869dd66b9bf5f3ad1a25
132300-132301 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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/27823/
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-04 13:06 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 13:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 14:21 dpdklab
2023-10-04 14:17 dpdklab
2023-10-04 14:14 dpdklab
2023-10-04 14:12 dpdklab
2023-10-04 14:10 dpdklab
2023-10-04 14:09 dpdklab
2023-10-04 14:08 dpdklab
2023-10-04 14:04 dpdklab
2023-10-04 14:03 dpdklab
2023-10-04 14:02 dpdklab
2023-10-04 14:01 dpdklab
2023-10-04 14:01 dpdklab
2023-10-04 13:58 dpdklab
2023-10-04 13:48 dpdklab
2023-10-04 13:48 dpdklab
2023-10-04 13:39 dpdklab
2023-10-04 13:37 dpdklab
2023-10-04 13:36 dpdklab
2023-10-04 13:34 dpdklab
2023-10-04 13:32 dpdklab
2023-10-04 13:28 dpdklab
2023-10-04 13:28 dpdklab
2023-10-04 13:26 dpdklab
2023-10-04 13:16 dpdklab
2023-10-04 13:13 dpdklab
2023-10-04 13:11 dpdklab
2023-10-04 13:11 dpdklab
2023-10-04 13:11 dpdklab
2023-10-04 13:09 dpdklab
2023-10-04 13:07 dpdklab
2023-10-04 13:07 dpdklab
2023-10-04 13:06 dpdklab
2023-10-04 13:06 dpdklab
2023-10-04 13:05 dpdklab
2023-10-04 13:05 dpdklab
2023-10-04 13:03 dpdklab
2023-10-04 13:02 dpdklab
2023-10-04 13:02 dpdklab
2023-10-04 12:59 dpdklab
2023-10-04 12:58 dpdklab
2023-10-04 12:58 dpdklab
2023-10-04 12:57 dpdklab
2023-10-04 12:57 dpdklab
2023-10-04 12:56 dpdklab
2023-10-04 12:56 dpdklab
2023-10-04 12:55 dpdklab
2023-10-04 12:55 dpdklab
2023-10-04 12:54 dpdklab
2023-10-04 12: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=651d6360.050a0220.d77ea.6f1fSMTPIN_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).