From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133765 [PATCH] [v3] net/iavf: fix mbuf release API selec
Date: Thu, 02 Nov 2023 11:23:39 -0700 (PDT) [thread overview]
Message-ID: <6543e92b.020a0220.6b9a.02c6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133765
_Functional Testing PASS_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Thursday, November 02 2023 04:43:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1025bd1c24b1be70e028c7ba0595782bce75fcc6
133765 --> 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
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28194/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-02 18:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 18:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-03 2:39 dpdklab
2023-11-02 20:39 dpdklab
2023-11-02 20:30 dpdklab
2023-11-02 20:12 dpdklab
2023-11-02 20:10 dpdklab
2023-11-02 20:04 dpdklab
2023-11-02 20:03 dpdklab
2023-11-02 19:58 dpdklab
2023-11-02 19:56 dpdklab
2023-11-02 19:53 dpdklab
2023-11-02 19:42 dpdklab
2023-11-02 19:38 dpdklab
2023-11-02 19:33 dpdklab
2023-11-02 19:29 dpdklab
2023-11-02 19:28 dpdklab
2023-11-02 19:28 dpdklab
2023-11-02 19:27 dpdklab
2023-11-02 19:26 dpdklab
2023-11-02 19:19 dpdklab
2023-11-02 19:18 dpdklab
2023-11-02 19:18 dpdklab
2023-11-02 19:16 dpdklab
2023-11-02 19:16 dpdklab
2023-11-02 19:13 dpdklab
2023-11-02 19:13 dpdklab
2023-11-02 19:13 dpdklab
2023-11-02 19:13 dpdklab
2023-11-02 19:09 dpdklab
2023-11-02 19:09 dpdklab
2023-11-02 19:08 dpdklab
2023-11-02 19:07 dpdklab
2023-11-02 19:02 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:51 dpdklab
2023-11-02 18:46 dpdklab
2023-11-02 18:41 dpdklab
2023-11-02 18:37 dpdklab
2023-11-02 18:37 dpdklab
2023-11-02 18:37 dpdklab
2023-11-02 18:19 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=6543e92b.020a0220.6b9a.02c6SMTPIN_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).