From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135732-135733 [PATCH] [v4,2/2] net/tap: fix buffer overf
Date: Thu, 04 Jan 2024 13:09:58 -0800 (PST) [thread overview]
Message-ID: <65971ea6.920a0220.13f82.089aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135733
_Functional Testing PASS_
Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Thursday, January 04 2024 17:51:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135732-135733 --> functional testing pass
Test environment and result as below:
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
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/3
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/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28792/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-04 21:10 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 21:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 8:09 dpdklab
2024-01-05 7:59 dpdklab
2024-01-05 0:16 dpdklab
2024-01-04 23:24 dpdklab
2024-01-04 23:07 dpdklab
2024-01-04 22:35 dpdklab
2024-01-04 22:33 dpdklab
2024-01-04 22:31 dpdklab
2024-01-04 22:20 dpdklab
2024-01-04 22:19 dpdklab
2024-01-04 22:13 dpdklab
2024-01-04 22:07 dpdklab
2024-01-04 22:06 dpdklab
2024-01-04 22:02 dpdklab
2024-01-04 22:01 dpdklab
2024-01-04 22:01 dpdklab
2024-01-04 21:59 dpdklab
2024-01-04 21:59 dpdklab
2024-01-04 21:59 dpdklab
2024-01-04 21:58 dpdklab
2024-01-04 21:58 dpdklab
2024-01-04 21:57 dpdklab
2024-01-04 21:57 dpdklab
2024-01-04 21:57 dpdklab
2024-01-04 21:56 dpdklab
2024-01-04 21:54 dpdklab
2024-01-04 21:47 dpdklab
2024-01-04 21:46 dpdklab
2024-01-04 21:46 dpdklab
2024-01-04 21:46 dpdklab
2024-01-04 21:46 dpdklab
2024-01-04 21:45 dpdklab
2024-01-04 21:45 dpdklab
2024-01-04 21:45 dpdklab
2024-01-04 21:45 dpdklab
2024-01-04 21:45 dpdklab
2024-01-04 21:44 dpdklab
2024-01-04 21:44 dpdklab
2024-01-04 21:43 dpdklab
2024-01-04 21:43 dpdklab
2024-01-04 21:43 dpdklab
2024-01-04 21:42 dpdklab
2024-01-04 21:42 dpdklab
2024-01-04 21:42 dpdklab
2024-01-04 21:41 dpdklab
2024-01-04 21:41 dpdklab
2024-01-04 21:41 dpdklab
2024-01-04 21:41 dpdklab
2024-01-04 21:40 dpdklab
2024-01-04 21:40 dpdklab
2024-01-04 21:40 dpdklab
2024-01-04 21:39 dpdklab
2024-01-04 21:39 dpdklab
2024-01-04 21:38 dpdklab
2024-01-04 21:38 dpdklab
2024-01-04 21:37 dpdklab
2024-01-04 21:29 dpdklab
2024-01-04 21:29 dpdklab
2024-01-04 21:17 dpdklab
2024-01-04 21:11 dpdklab
2024-01-04 21:10 dpdklab
2024-01-04 21:05 dpdklab
2024-01-04 21:04 dpdklab
2024-01-04 21:03 dpdklab
2024-01-04 21:03 dpdklab
2024-01-04 21:00 dpdklab
2024-01-04 20:52 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=65971ea6.920a0220.13f82.089aSMTPIN_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).