From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw123774 [PATCH] [v3] net/iavf: add debug checks for mbuf
Date: Mon, 13 Feb 2023 04:02:01 -0500 (EST) [thread overview]
Message-ID: <20230213090201.92ADA456@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/123774
_Functional Testing PASS_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Monday, February 13 2023 08:31:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39d469a7eb4f157923be73aea0b0cc1015860ca7
123774 --> 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 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25368/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-13 9:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 9:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-15 10:00 dpdklab
2023-02-14 19:52 dpdklab
[not found] <20230213083150.295194-1-mingjinx.ye@intel.com>
2023-02-13 8:24 ` |SUCCESS| pw123774 [PATCH v3] " qemudev
2023-02-13 8:28 ` qemudev
2023-02-13 8:35 ` checkpatch
2023-02-14 0:19 ` 0-day Robot
2023-02-13 17:42 |SUCCESS| pw123774 [PATCH] [v3] " dpdklab
2023-02-13 17:41 dpdklab
2023-02-13 17:35 dpdklab
2023-02-13 17:34 dpdklab
2023-02-13 17:32 dpdklab
2023-02-13 17:26 dpdklab
2023-02-13 17:23 dpdklab
2023-02-13 17:21 dpdklab
2023-02-13 17:14 dpdklab
2023-02-13 17:13 dpdklab
2023-02-13 17:08 dpdklab
2023-02-13 17:04 dpdklab
2023-02-13 16:51 dpdklab
2023-02-13 16:49 dpdklab
2023-02-13 15:10 dpdklab
2023-02-13 10:13 dpdklab
2023-02-13 9:22 dpdklab
2023-02-13 9:19 dpdklab
2023-02-13 9:16 dpdklab
2023-02-13 9:16 dpdklab
2023-02-13 9:16 dpdklab
2023-02-13 9:12 dpdklab
2023-02-13 9:08 dpdklab
2023-02-13 9:06 dpdklab
2023-02-13 9:04 dpdklab
2023-02-13 9:03 dpdklab
2023-02-13 8:59 dpdklab
2023-02-13 8:59 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=20230213090201.92ADA456@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).