From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129741-129747 [PATCH] [v2,7/7] dma/cnxk: add completion
Date: Mon, 31 Jul 2023 05:47:46 -0700 (PDT) [thread overview]
Message-ID: <64c7ad72.0d0a0220.e2364.da5fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129747
_Functional Testing PASS_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Monday, July 31 2023 12:12:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:12fcafcd62286933e6b167b14856d21f642efa5f
129741-129747 --> 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
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27165/
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-31 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 12:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-31 23:44 dpdklab
2023-07-31 17:04 dpdklab
2023-07-31 16:51 dpdklab
2023-07-31 15:54 dpdklab
2023-07-31 15:33 dpdklab
2023-07-31 15:25 dpdklab
2023-07-31 15:04 dpdklab
2023-07-31 13:39 dpdklab
2023-07-31 13:09 dpdklab
2023-07-31 13:06 dpdklab
2023-07-31 12:54 dpdklab
2023-07-31 12:54 dpdklab
2023-07-31 12:52 dpdklab
2023-07-31 12:51 dpdklab
2023-07-31 12:49 dpdklab
2023-07-31 12:42 dpdklab
2023-07-31 12:41 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=64c7ad72.0d0a0220.e2364.da5fSMTPIN_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).