From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw158325 [PATCH] graph: fix use-after-free when updating e
Date: Fri, 31 Oct 2025 15:59:52 -0700 (PDT) [thread overview]
Message-ID: <69053f68.050a0220.37c033.3dc0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251031221304.394997-2-rjarry@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/158325
_Functional Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Friday, October 31 2025 22:13:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8c4861d00aabcf54ef9d6f1df2a4cfb37c06f6c2
158325 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#252331
Test environment and result as below:
Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps
Aggregate Results by Test Suite
+--------------------+--------+
| Test Suite | Result |
+====================+========+
| blocklist | PASS |
+--------------------+--------+
| promisc_support | PASS |
+--------------------+--------+
| uni_pkt | PASS |
+--------------------+--------+
| dynamic_queue_conf | PASS |
+--------------------+--------+
| hello_world | PASS |
+--------------------+--------+
| l2fwd | PASS |
+--------------------+--------+
| softnic | PASS |
+--------------------+--------+
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34436/
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-10-31 22:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251031221304.394997-2-rjarry@redhat.com>
2025-10-31 21:40 ` |SUCCESS| pw158325 [PATCH dpdk] graph: fix use-after-free when updating edges with active graphs qemudev
2025-10-31 21:45 ` qemudev
2025-10-31 22:13 ` checkpatch
2025-10-31 22:41 ` |PENDING| pw158325 [PATCH] graph: fix use-after-free when updating e dpdklab
2025-10-31 22:42 ` dpdklab
2025-10-31 22:43 ` |SUCCESS| " dpdklab
2025-10-31 22:43 ` |PENDING| " dpdklab
2025-10-31 22:45 ` dpdklab
2025-10-31 22:47 ` |SUCCESS| " dpdklab
2025-10-31 22:50 ` |FAILURE| " dpdklab
2025-10-31 22:50 ` dpdklab
2025-10-31 22:51 ` |PENDING| " dpdklab
2025-10-31 22:59 ` dpdklab [this message]
2025-10-31 23:03 ` |SUCCESS| " dpdklab
2025-10-31 23:03 ` |WARNING| " dpdklab
2025-10-31 23:05 ` |SUCCESS| " dpdklab
2025-10-31 23:12 ` |WARNING| " dpdklab
2025-10-31 23:17 ` |SUCCESS| pw158325 [PATCH dpdk] graph: fix use-after-free when updating edges with active graphs 0-day Robot
2025-10-31 23:17 ` 0-day Robot
2025-10-31 23:23 ` |SUCCESS| pw158325 [PATCH] graph: fix use-after-free when updating e dpdklab
2025-10-31 23:25 ` dpdklab
2025-10-31 23:26 ` |WARNING| " dpdklab
2025-10-31 23:28 ` |SUCCESS| " dpdklab
2025-10-31 23:30 ` dpdklab
2025-11-01 0:16 ` dpdklab
2025-11-01 2:17 ` 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=69053f68.050a0220.37c033.3dc0SMTPIN_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).