From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152164 [PATCH] acl: use common top-level variable for ea
Date: Mon, 03 Mar 2025 15:14:36 -0800 (PST) [thread overview]
Message-ID: <67c637dc.920a0220.6245a.f061SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1740768356-29954-1-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152164
_Functional Testing PASS_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Friday, February 28 2025 18:45:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa
152164 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#215476
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/32721/
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-03-03 23:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1740768356-29954-1-git-send-email-andremue@linux.microsoft.com>
2025-02-28 18:13 ` |SUCCESS| pw152164 [PATCH] acl: use common top-level variable for easier maintenance qemudev
2025-02-28 18:17 ` qemudev
2025-02-28 18:46 ` checkpatch
2025-02-28 20:05 ` 0-day Robot
2025-03-01 6:32 ` |SUCCESS| pw152164 [PATCH] acl: use common top-level variable for ea dpdklab
2025-03-01 6:56 ` dpdklab
2025-03-01 7:08 ` dpdklab
2025-03-01 7:23 ` dpdklab
2025-03-01 7:32 ` dpdklab
2025-03-01 7:36 ` dpdklab
2025-03-01 7:43 ` dpdklab
2025-03-01 7:47 ` dpdklab
2025-03-01 8:02 ` dpdklab
2025-03-01 8:14 ` dpdklab
2025-03-01 8:25 ` dpdklab
2025-03-01 8:27 ` dpdklab
2025-03-01 8:32 ` |PENDING| " dpdklab
2025-03-01 8:41 ` |SUCCESS| " dpdklab
2025-03-01 9:03 ` dpdklab
2025-03-01 9:06 ` dpdklab
2025-03-01 9:14 ` dpdklab
2025-03-01 9:15 ` dpdklab
2025-03-01 10:14 ` |PENDING| " dpdklab
2025-03-01 10:25 ` dpdklab
2025-03-01 11:25 ` dpdklab
2025-03-01 11:28 ` |SUCCESS| " dpdklab
2025-03-01 11:29 ` |PENDING| " dpdklab
2025-03-01 11:32 ` |SUCCESS| " dpdklab
2025-03-01 12:04 ` |PENDING| " dpdklab
2025-03-01 12:12 ` |SUCCESS| " dpdklab
2025-03-01 12:25 ` |PENDING| " dpdklab
2025-03-01 12:41 ` |SUCCESS| " dpdklab
2025-03-01 13:27 ` dpdklab
2025-03-01 13:36 ` dpdklab
2025-03-01 19:04 ` dpdklab
2025-03-01 19:49 ` dpdklab
2025-03-02 0:16 ` dpdklab
2025-03-02 0:30 ` dpdklab
2025-03-02 4:43 ` dpdklab
2025-03-02 4:45 ` dpdklab
2025-03-02 4:48 ` dpdklab
2025-03-02 4:49 ` dpdklab
2025-03-02 15:13 ` dpdklab
2025-03-02 15:45 ` dpdklab
2025-03-03 23:14 ` dpdklab [this message]
2025-03-03 23:20 ` 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=67c637dc.920a0220.6245a.f061SMTPIN_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).