From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153071 [PATCH] net/mlx5: fix out-of-bounds write in Rx s
Date: Tue, 22 Apr 2025 06:35:48 -0700 (PDT) [thread overview]
Message-ID: <68079b34.170a0220.ee3f0.c8a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250422063754.3429965-1-patrykochal@gmail.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153071
_Functional Testing PASS_
Submitter: patryk ochal <patrykochal@gmail.com>
Date: Tuesday, April 22 2025 06:37:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:edd3f4b1265e6da707c46ca9b6c39d332647baea
153071 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#222559
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/33048/
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-04-22 13:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250422063754.3429965-1-patrykochal@gmail.com>
2025-04-22 6:05 ` |SUCCESS| pw153071 [PATCH] net/mlx5: fix out-of-bounds write in Rx software ring qemudev
2025-04-22 6:09 ` qemudev
2025-04-22 6:40 ` checkpatch
2025-04-22 13:25 ` |SUCCESS| pw153071 [PATCH] net/mlx5: fix out-of-bounds write in Rx s dpdklab
2025-04-22 13:35 ` dpdklab [this message]
2025-04-22 13:37 ` dpdklab
2025-04-22 13:43 ` dpdklab
2025-04-22 13:48 ` dpdklab
2025-04-22 13:49 ` dpdklab
2025-04-22 13:52 ` dpdklab
2025-04-22 13:59 ` dpdklab
2025-04-22 14:01 ` |FAILURE| " dpdklab
2025-04-22 14:02 ` |PENDING| " dpdklab
2025-04-22 14:04 ` |SUCCESS| " dpdklab
2025-04-22 14:09 ` |FAILURE| " dpdklab
2025-04-22 14:09 ` dpdklab
2025-04-22 14:11 ` dpdklab
2025-04-22 14:13 ` |SUCCESS| " dpdklab
2025-04-22 14:16 ` |FAILURE| " dpdklab
2025-04-22 14:23 ` dpdklab
2025-04-22 14:24 ` dpdklab
2025-04-22 14:24 ` dpdklab
2025-04-22 14:26 ` dpdklab
2025-04-22 14:27 ` dpdklab
2025-04-22 14:31 ` dpdklab
2025-04-22 14:38 ` |WARNING| " dpdklab
2025-04-22 14:39 ` dpdklab
2025-04-22 14:50 ` |SUCCESS| " dpdklab
2025-04-22 14:50 ` dpdklab
2025-04-22 14:51 ` dpdklab
2025-04-22 15:05 ` |FAILURE| " dpdklab
2025-04-22 15:13 ` dpdklab
2025-04-22 15:15 ` dpdklab
2025-04-22 15:16 ` dpdklab
2025-04-22 15:22 ` |WARNING| " dpdklab
2025-04-22 15:25 ` |FAILURE| " dpdklab
2025-04-22 15:26 ` dpdklab
2025-04-22 15:30 ` |WARNING| " dpdklab
2025-04-22 15:47 ` |FAILURE| " dpdklab
2025-04-22 16:05 ` dpdklab
2025-04-22 17:01 ` 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=68079b34.170a0220.ee3f0.c8a2SMTPIN_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).