From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128638-128639 [PATCH] [v2,5/5] net/mlx5: add Tx datapath
Date: Thu, 15 Jun 2023 07:03:30 -0700 (PDT) [thread overview]
Message-ID: <648b1a32.250a0220.3b903.b6b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128639
_Testing PASS_
Submitter: Slava Ovsiienko <viacheslavo@nvidia.com>
Date: Tuesday, June 13 2023 16:58:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:050de60d8a5cef8b7c10b4471905ca8bf69d670e
128638-128639 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
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/26669/
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-15 14:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 14:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-15 21:21 dpdklab
2023-06-15 21:09 dpdklab
2023-06-15 20:40 dpdklab
2023-06-15 20:35 dpdklab
2023-06-15 20:06 dpdklab
2023-06-15 14:03 dpdklab
2023-06-15 9:40 dpdklab
2023-06-15 6:37 dpdklab
2023-06-15 3:55 dpdklab
2023-06-15 3:40 dpdklab
2023-06-15 3:39 dpdklab
2023-06-15 3:31 dpdklab
2023-06-15 3:30 dpdklab
2023-06-15 3:27 dpdklab
2023-06-15 3:23 dpdklab
2023-06-15 3:21 dpdklab
2023-06-15 3:15 dpdklab
2023-06-15 3:15 dpdklab
2023-06-15 3:14 dpdklab
2023-06-15 3:12 dpdklab
2023-06-15 3:11 dpdklab
2023-06-15 3:11 dpdklab
2023-06-15 2:59 dpdklab
2023-06-15 2:59 dpdklab
2023-06-15 2:59 dpdklab
2023-06-15 2:50 dpdklab
2023-06-15 2:50 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=648b1a32.250a0220.3b903.b6b6SMTPIN_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).