automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153011 [PATCH] rust: RFC/demo of safe API for Dpdk Eal,
Date: Thu, 17 Apr 2025 08:51:39 -0700 (PDT)	[thread overview]
Message-ID: <6801238b.c80a0220.c1fb3.02a3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250417151039.186448-1-harry.van.haaren@intel.com>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153011

_Functional Testing PASS_

Submitter: Harry van Haaren <harry.van.haaren@intel.com>
Date: Thursday, April 17 2025 15:10:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ca1690ebd224f148268285b15b97441ccdbdd07e

153011 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#222082

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  |
+----------------+--------+
| dynamic_queue  |  PASS  |
+----------------+--------+
| rxtx_callbacks |  PASS  |
+----------------+--------+


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33029/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-04-17 15:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250417151039.186448-1-harry.van.haaren@intel.com>
2025-04-17 14:37 ` |SUCCESS| pw153011 [PATCH] rust: RFC/demo of safe API for Dpdk Eal, Eth and Rxq qemudev
2025-04-17 14:42 ` qemudev
2025-04-17 15:12 ` |WARNING| " checkpatch
2025-04-17 15:43 ` |SUCCESS| pw153011 [PATCH] rust: RFC/demo of safe API for Dpdk Eal, dpdklab
2025-04-17 15:50 ` |PENDING| " dpdklab
2025-04-17 15:50 ` |SUCCESS| " dpdklab
2025-04-17 15:51 ` dpdklab [this message]
2025-04-17 15:58 ` dpdklab
2025-04-17 15:59 ` |PENDING| " dpdklab
2025-04-17 16:00 ` dpdklab
2025-04-17 16:03 ` |SUCCESS| " dpdklab
2025-04-17 16:05 ` dpdklab
2025-04-17 16:06 ` dpdklab
2025-04-17 16:17 ` dpdklab
2025-04-17 16:30 ` dpdklab
2025-04-17 16:58 ` dpdklab
2025-04-17 17:03 ` dpdklab
2025-04-17 17:11 ` dpdklab
2025-04-17 17:26 ` dpdklab
2025-04-17 17:27 ` dpdklab
2025-04-17 17:54 ` dpdklab
2025-04-17 18:15 ` 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=6801238b.c80a0220.c1fb3.02a3SMTPIN_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).