From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155691 [PATCH] app/graph: fix overrun error (destination
Date: Thu, 07 Aug 2025 06:22:05 -0700 (PDT) [thread overview]
Message-ID: <6894a87d.170a0220.15ebda.58deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250807110640.1094029-1-14pwcse1224@uetpeshawar.edu.pk>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155691
_Functional Testing PASS_
Submitter: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Date: Thursday, August 07 2025 11:06:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:38543d33bd47fc0ee21f59db80a8763620741879
155691 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#239499
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+----------------+--------+
| Test Suite | Result |
+================+========+
| cmdline | PASS |
+----------------+--------+
| rxtx_callbacks | PASS |
+----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33830/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-08-07 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250807110640.1094029-1-14pwcse1224@uetpeshawar.edu.pk>
2025-08-07 10:33 ` |SUCCESS| pw155691 [PATCH] app/graph: fix overrun error (destination buffer too small) qemudev
2025-08-07 10:38 ` qemudev
2025-08-07 11:05 ` |SUCCESS| pw155691 [PATCH] app/graph: fix overrun error destination buffer too small checkpatch
2025-08-07 12:45 ` |SUCCESS| pw155691 [PATCH] app/graph: fix overrun error (destination buffer too small) 0-day Robot
2025-08-07 13:03 ` |SUCCESS| pw155691 [PATCH] app/graph: fix overrun error (destination dpdklab
2025-08-07 13:22 ` dpdklab [this message]
2025-08-07 13:27 ` dpdklab
2025-08-07 13:29 ` |PENDING| " dpdklab
2025-08-07 13:32 ` |SUCCESS| " dpdklab
2025-08-07 13:35 ` dpdklab
2025-08-07 13:39 ` dpdklab
2025-08-07 13:39 ` dpdklab
2025-08-07 13:47 ` dpdklab
2025-08-07 13:48 ` |PENDING| " dpdklab
2025-08-07 13:52 ` |SUCCESS| " dpdklab
2025-08-07 14:31 ` dpdklab
2025-08-07 14:31 ` dpdklab
2025-08-07 15:08 ` dpdklab
2025-08-07 15:31 ` 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=6894a87d.170a0220.15ebda.58deSMTPIN_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).