From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154285 [PATCH] [RFC] fib6: implement RCU rule reclamatio
Date: Tue, 10 Jun 2025 11:04:23 -0700 (PDT) [thread overview]
Message-ID: <684873a7.d40a0220.111a62.c0d8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250610145341.38271-2-rjarry@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154285
_Functional Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Tuesday, June 10 2025 14:53:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e3942de6c981e14a762185976a84cb02882699ed
154285 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#230003
Test environment and result as below:
Ubuntu 24.04 LTS
Kernel: 6.8.0-55-generic
Compiler: gcc 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/33378/
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-06-10 18:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250610145341.38271-2-rjarry@redhat.com>
2025-06-10 14:25 ` |SUCCESS| pw154285 [RFC PATCH dpdk] fib6: implement RCU rule reclamation qemudev
2025-06-10 14:29 ` |FAILURE| " qemudev
2025-06-10 14:54 ` |WARNING| " checkpatch
2025-06-10 16:04 ` |FAILURE| " 0-day Robot
2025-06-10 18:04 ` dpdklab [this message]
2025-06-10 18:06 ` |SUCCESS| pw154285 [PATCH] [RFC] fib6: implement RCU rule reclamatio dpdklab
2025-06-10 18:21 ` dpdklab
2025-06-10 18:36 ` |PENDING| " dpdklab
2025-06-10 18:54 ` |WARNING| " dpdklab
2025-06-10 19:02 ` dpdklab
2025-06-10 19:23 ` |SUCCESS| " dpdklab
2025-06-10 19:28 ` |WARNING| " dpdklab
2025-06-10 20:25 ` |FAILURE| " dpdklab
2025-06-10 20:29 ` |SUCCESS| " dpdklab
2025-06-10 20:29 ` dpdklab
2025-06-10 20:59 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 21:02 ` dpdklab
2025-06-10 22:12 ` |FAILURE| " dpdklab
2025-06-11 2:24 ` |PENDING| " dpdklab
2025-06-11 2:28 ` |WARNING| " dpdklab
2025-06-11 2:29 ` dpdklab
2025-06-11 2:29 ` dpdklab
2025-06-11 2:30 ` dpdklab
2025-06-11 2:30 ` dpdklab
2025-06-11 2:31 ` dpdklab
2025-06-11 2:32 ` dpdklab
2025-06-11 4:10 ` |SUCCESS| " dpdklab
2025-06-11 6:49 ` |FAILURE| " dpdklab
2025-06-11 8:47 ` |SUCCESS| " dpdklab
2025-06-11 8:49 ` |FAILURE| " 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=684873a7.d40a0220.111a62.c0d8SMTPIN_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).