From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129447-129449 [PATCH] [v6,2/2] doc: add mlx5 datapath tr
Date: Tue, 11 Jul 2023 15:40:07 -0700 (PDT) [thread overview]
Message-ID: <64adda47.810a0220.dfb76.d22cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129449
_Testing PASS_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Tuesday, July 11 2023 15:15:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:623dc9364dc6a818799941cc26dc8f70feb2bb24
129447-129449 --> testing pass
Test environment and result as below:
+-------------+----------+
| Environment | abi_test |
+=============+==========+
| RHEL 7 | PASS |
+-------------+----------+
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27041/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-11 22:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 22:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-12 13:43 dpdklab
2023-07-12 11:43 dpdklab
2023-07-12 10:53 dpdklab
2023-07-12 10:35 dpdklab
2023-07-12 10:28 dpdklab
2023-07-12 10:23 dpdklab
2023-07-12 5:16 dpdklab
2023-07-12 1:33 dpdklab
2023-07-11 23:57 dpdklab
2023-07-11 23:32 dpdklab
2023-07-11 23:20 dpdklab
2023-07-11 23:19 dpdklab
2023-07-11 23:14 dpdklab
2023-07-11 23:11 dpdklab
2023-07-11 23:07 dpdklab
2023-07-11 23:07 dpdklab
2023-07-11 23:06 dpdklab
2023-07-11 23:05 dpdklab
2023-07-11 23:04 dpdklab
2023-07-11 23:03 dpdklab
2023-07-11 22:46 dpdklab
2023-07-11 18:26 dpdklab
2023-07-11 18:22 dpdklab
2023-07-11 17:41 dpdklab
2023-07-11 17:40 dpdklab
2023-07-11 17:39 dpdklab
2023-07-11 17:10 dpdklab
2023-07-11 17:09 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=64adda47.810a0220.dfb76.d22cSMTPIN_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).