From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127734 [PATCH] [v5] ethdev: add flow item for RoCE infin
Date: Fri, 09 Jun 2023 15:57:58 -0700 (PDT) [thread overview]
Message-ID: <6483ae76.050a0220.8c4c.891eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/127734
_Testing PASS_
Submitter: Dong Zhou <dongzhou@nvidia.com>
Date: Wednesday, May 31 2023 03:26:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c9df59bcc9bec67783de98486879594e52bdc418
127734 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26459/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-09 22:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 22:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 22:58 dpdklab
2023-06-09 22:58 dpdklab
2023-06-09 22:58 dpdklab
2023-06-08 22:26 dpdklab
2023-06-08 22:22 dpdklab
2023-05-31 5:38 dpdklab
2023-05-31 5:31 dpdklab
2023-05-31 5:02 dpdklab
2023-05-31 4:48 dpdklab
2023-05-31 4:31 dpdklab
2023-05-31 4:18 dpdklab
2023-05-31 4:05 dpdklab
2023-05-31 4:05 dpdklab
2023-05-31 3:58 dpdklab
2023-05-31 3:58 dpdklab
2023-05-31 3:57 dpdklab
2023-05-31 3:53 dpdklab
2023-05-31 3:52 dpdklab
2023-05-31 3:52 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=6483ae76.050a0220.8c4c.891eSMTPIN_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).