From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127564-127565 [PATCH] [2/2] common/cnxk: add new APIs fo
Date: Fri, 26 May 2023 14:59:25 -0700 (PDT) [thread overview]
Message-ID: <64712bbd.170a0220.e6793.72afSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/127565
_Functional Testing PASS_
Submitter: Ashwin Sekhar T K <asekhar@marvell.com>
Date: Friday, May 26 2023 13:45:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c9df59bcc9bec67783de98486879594e52bdc418
127564-127565 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26417/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-26 21:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 21:59 dpdklab [this message]
2023-05-26 22:01 dpdklab
2023-05-26 22:05 dpdklab
2023-05-26 22:06 dpdklab
2023-05-26 22:07 dpdklab
2023-05-26 22:13 dpdklab
2023-05-26 22:20 dpdklab
2023-05-26 22:22 dpdklab
2023-05-26 22:25 dpdklab
2023-05-26 22:25 dpdklab
2023-05-26 22:27 dpdklab
2023-05-26 22:32 dpdklab
2023-05-26 22:34 dpdklab
2023-05-26 22:41 dpdklab
2023-05-26 22:42 dpdklab
2023-05-26 22:43 dpdklab
2023-05-26 22:50 dpdklab
2023-05-26 22:51 dpdklab
2023-05-26 22:58 dpdklab
2023-05-26 23:05 dpdklab
2023-05-26 23:06 dpdklab
2023-05-26 23:08 dpdklab
2023-05-26 23:19 dpdklab
2023-05-26 23:23 dpdklab
2023-05-26 23:29 dpdklab
2023-05-26 23:33 dpdklab
2023-05-26 23:46 dpdklab
2023-05-27 0:08 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=64712bbd.170a0220.e6793.72afSMTPIN_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).