From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129690-129691 [PATCH] [v12,2/2] net/i40e: replace put fu
Date: Fri, 21 Jul 2023 10:48:01 -0700 (PDT) [thread overview]
Message-ID: <64bac4d1.810a0220.a2970.0f6cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129691
_Functional Testing PASS_
Submitter: Dharmik Thakkar <dharmikjayesh.thakkar@arm.com>
Date: Friday, July 21 2023 16:28:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fbafb3676c482dab60c0b5465b47f2ea33893a36
129690-129691 --> functional testing pass
Test environment and result as below:
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/27129/
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-21 17:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 17:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 0:19 dpdklab
2023-07-25 0:18 dpdklab
2023-07-24 1:42 dpdklab
2023-07-24 1:38 dpdklab
2023-07-24 0:58 dpdklab
2023-07-24 0:56 dpdklab
2023-07-24 0:51 dpdklab
2023-07-21 22:34 dpdklab
2023-07-21 21:11 dpdklab
2023-07-21 19:38 dpdklab
2023-07-21 18:32 dpdklab
2023-07-21 18:22 dpdklab
2023-07-21 18:11 dpdklab
2023-07-21 18:10 dpdklab
2023-07-21 18:10 dpdklab
2023-07-21 18:09 dpdklab
2023-07-21 18:06 dpdklab
2023-07-21 18:05 dpdklab
2023-07-21 18:05 dpdklab
2023-07-21 18:04 dpdklab
2023-07-21 18:03 dpdklab
2023-07-21 18:03 dpdklab
2023-07-21 17:58 dpdklab
2023-07-21 17:54 dpdklab
2023-07-21 17:52 dpdklab
2023-07-21 17:51 dpdklab
2023-07-21 17:50 dpdklab
2023-07-21 17:44 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=64bac4d1.810a0220.a2970.0f6cSMTPIN_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).