From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135230 [PATCH] [v2] net/tap: fix buffer overflow for pty
Date: Fri, 15 Dec 2023 09:24:31 -0800 (PST) [thread overview]
Message-ID: <657c8bcf.0d0a0220.edef7.872fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135230
_Testing PASS_
Submitter: Sivaramakrishnan, VenkatX <venkatx.sivaramakrishnan@intel.com>
Date: Friday, December 15 2023 13:38:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135230 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28649/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-15 17:24 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 17:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 22:13 dpdklab
2023-12-15 17:37 dpdklab
2023-12-15 17:32 dpdklab
2023-12-15 17:29 dpdklab
2023-12-15 17:29 dpdklab
2023-12-15 17:28 dpdklab
2023-12-15 17:26 dpdklab
2023-12-15 17:26 dpdklab
2023-12-15 17:24 dpdklab
2023-12-15 17:22 dpdklab
2023-12-15 17:21 dpdklab
2023-12-15 17:19 dpdklab
2023-12-15 17:17 dpdklab
2023-12-15 17:15 dpdklab
2023-12-15 17:15 dpdklab
2023-12-15 17:14 dpdklab
2023-12-15 17:13 dpdklab
2023-12-15 17:12 dpdklab
2023-12-15 17:11 dpdklab
2023-12-15 17:11 dpdklab
2023-12-15 17:11 dpdklab
2023-12-15 17:10 dpdklab
2023-12-15 17:10 dpdklab
2023-12-15 17:10 dpdklab
2023-12-15 17:09 dpdklab
2023-12-15 17:08 dpdklab
2023-12-15 17:08 dpdklab
2023-12-15 17:08 dpdklab
2023-12-15 17:07 dpdklab
2023-12-15 17:07 dpdklab
2023-12-15 17:07 dpdklab
2023-12-15 17:06 dpdklab
2023-12-15 17:06 dpdklab
2023-12-15 17:04 dpdklab
2023-12-15 17:04 dpdklab
2023-12-15 17:03 dpdklab
2023-12-15 17:03 dpdklab
2023-12-15 17:02 dpdklab
2023-12-15 17:02 dpdklab
2023-12-15 17:00 dpdklab
2023-12-15 16:59 dpdklab
2023-12-15 16:59 dpdklab
2023-12-15 16:58 dpdklab
2023-12-15 16:57 dpdklab
2023-12-15 16:57 dpdklab
2023-12-15 16:56 dpdklab
2023-12-15 16:56 dpdklab
2023-12-15 16:56 dpdklab
2023-12-15 16:56 dpdklab
2023-12-15 16:56 dpdklab
2023-12-15 16:56 dpdklab
2023-12-15 16:56 dpdklab
2023-12-15 16:55 dpdklab
2023-12-15 16:55 dpdklab
2023-12-15 16:55 dpdklab
2023-12-15 16:54 dpdklab
2023-12-15 16:54 dpdklab
2023-12-15 16:54 dpdklab
2023-12-15 16:53 dpdklab
2023-12-15 16:53 dpdklab
2023-12-15 16:53 dpdklab
2023-12-15 16:53 dpdklab
2023-12-15 16:52 dpdklab
2023-12-15 16:52 dpdklab
2023-12-15 16:39 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=657c8bcf.0d0a0220.edef7.872fSMTPIN_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).